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.
npx agentmods add commands/raulvidis/openclaw-multi-agent-kit/fixgit clone --depth 1 https://github.com/raulvidis/openclaw-multi-agent-kitWhat 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 | $0.00008 | $0.00189 |
| Opus 5 | $0.00004 | $0.00095 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
fix 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 2d 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.
What it actually says
Run the repo's quality gates and fix every failure until green:
- JSON examples validate: !
python3 -m json.tool examples/full-team.json > /dev/null && python3 -m json.tool examples/minimal-team.json > /dev/null && echo JSON-OK - Docs front matter:
python3 .agents/skills/docs-list/scripts/docs-list.py - Template hygiene: SOUL.md/SKILL.md frontmatter at line 1; placeholders (
[Your ...],YOUR_*,{WORKSPACE}) not replaced with real values; no model ids pinned - Examples in sync: full-team.json = 10 core agents, minimal-team.json = 3, both without
modelfields
Re-run until clean. Update docs/CHANGELOG for visible changes.
Confirm git status -sb clean and on the expected branch.
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.
- 2d ago First seen · 12 lines · 8 tokens per session scan A d41cd70de7ac
fix is a command published in the GitHub repository raulvidis/openclaw-multi-agent-kit (395 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 189 once invoked, about $0.0000 per session on Opus 5. 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.