Claw Code is a Rust implementation of a command-line agent harness, maintained as an agent-managed repository rather than a conventional manually operated product. Its harnesses plan, execute, verify, label, and preserve the project, while the catalogue add-ons support the agent workflows around it.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ultraworkers/claw-codeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ultraworkers/claw-code/agents)<a href="https://agentmods.dev/commands/ultraworkers/claw-code/agents"><img src="https://agentmods.dev/badge/commands/ultraworkers/claw-code/agents/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ultraworkers/claw-code/agents"><img src="https://agentmods.dev/badge/commands/ultraworkers/claw-code/agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00818 |
| Opus 5.5 | $0.00000 | $0.00327 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
AGENTS scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commands crate
OVERVIEW
REPL slash-command surface: parsing, spec registry, help rendering, and a handful of in-crate handlers. Single flat src/lib.rs (~7k lines). Deps: plugins, runtime, serde_json only. Note: tools depends on commands, not the reverse.
lib.rs MAP
| Lines | Landmark |
|---|---|
| 16–58 | Registry types: CommandManifestEntry, CommandSource (Builtin / InternalOnly / FeatureGated), CommandRegistry, SlashCommandSpec, SkillSlashDispatch |
| 60–1047 | SLASH_COMMAND_SPECS static table. 120+ entries (help, status, sandbox, compact, model, permissions, clear, cost, resume, config, mcp, memory, init, diff, version, bughunter, commit, pr, issue, ultraplan, teleport, debug-tool-call, export, session, plugin, agents, skills, doctor, plan, review, tasks, theme, vim, voice, chat, ...) |
| 1048–1303 | SlashCommand enum (~65 variants + Unknown(String)), SlashCommandParseError, SlashCommand::parse (L1218) |
| 1515–1899 | Per-command arg parsers: parse_mcp_command, parse_plugin_command, parse_session_command, etc. |
| 1900–2108 | Help/suggestion rendering: render_slash_command_help*, suggest_slash_commands (Levenshtein), category grouping |
| 2109–2682 | Result types + handlers: handle_plugins_slash_command, handle_agents/mcp/skills_slash_command(_json), skill dispatch/resolve |
| 3160–5293 | Reporting layer: paired text and _json renderers for plugins/agents/skills/mcp reports, skill install/uninstall/create-agent logic, frontmatter parsing, root discovery |
| 5294 | handle_slash_command(input, session, compaction) top dispatch. Only Compact and Help execute here; all other variants return to the REPL caller |
| 5403–7183 | mod tests (~1780 lines) |
ADDING A SLASH COMMAND
- Spec. Add a
SlashCommandSpecentry toSLASH_COMMAND_SPECS. Setresume_supportedhonestly. - Enum + parse. Add a variant to
SlashCommand. Wire a match arm inSlashCommand::parse. If the command takes arguments, add a dedicatedparse_*_commandfunction in the arg-parser block. - Handler. Decide where execution lives:
- In-crate (like Compact/Help): handle it inside
handle_slash_command. - Returned to caller: just return the parsed variant. The REPL layer executes it.
- In-crate (like Compact/Help): handle it inside
- Help. Make sure the spec's
summaryandargument_hintare set so help rendering and suggestion matching pick it up automatically. - Tests. Cover parsing (valid input, bad input, edge cases) in the inline
mod tests.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 38 lines · 0 tokens per session scan A befc94be73ad
AGENTS is a command published in the GitHub repository ultraworkers/claw-code (194,922 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 818 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.