Built-in workflows and marketplace
open·kritt comes with a small set of basic workflows already installed. They appear on the Workflows page when the system starts, so you can inspect their steps and use one for a scan without building every prompt from scratch.
Built-in workflows are starting points, not black boxes. Read their prompts and output schemas, check that their assumptions fit the codebase and configuration you are scanning, and adapt the pattern when your target needs something more specific.
The first security workflow
The first workflow we provide uses a battle-proven pattern for node and protocol codebases:
Enumerate entrypoints
Scan the codebase once to identify externally reachable entrypoints and the handlers that process attacker-controlled input.
Pair each entrypoint with an impact
Fan out the enumerated entrypoints across three focused security targets:
- Node crash - can this input stop or destabilize a node?
- Consensus violation - can it make nodes disagree or violate protocol rules?
- Loss of funds - can it lead to unauthorized or incorrect asset movement?
Investigate focused units of work
Give each downstream agent one entrypoint and one impact target to trace and verify.
This decomposition saves context. Entrypoints are discovered once instead of being rediscovered by every agent, and each downstream run spends its context window on one concrete entrypoint-impact pair. That produces smaller prompts, broader systematic coverage, and more room for the agent to follow code paths and validate a finding.
Open workflow marketplace
We plan to add an open workflow marketplace where researchers and teams can publish, discover, install, fork, and improve workflows. The goal is to make proven research patterns reusable while keeping every workflow inspectable and adaptable to a target.
The marketplace is upcoming. Until it is available, use the built-in workflows or create your own in the workflow builder.