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/done-0/openarche/rungit clone --depth 1 https://github.com/Done-0/openarcheWhat 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.00007 | $0.00288 |
| Opus 5 | $0.00003 | $0.00144 |
| Sonnet 5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
run 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
Use this command to inspect, draft, revise, or save a real runbook.
Required behavior:
- Prefer an existing plan when one exists.
- Build a runbook that stays aligned with the current harness structure:
- execution isolation
- validation protocol
- observability protocol when required
- review loop
- maintenance follow-up
- Keep the runbook aligned with current product behavior:
- execution must follow the configured isolation strategy
- OpenArche may write the isolation plan and setup commands, but it does not automatically mutate the user's git workspace
- validation must include acceptance checks and regression checks
- observability is only required when it is enabled and relevant services exist
- review must reflect enabled review paths and merge checks
- maintenance must reflect the current cleanup and knowledge-capture requirements
When presenting the runbook, organize it into:
- execution isolation
- validation
- observability
- review
- maintenance
Prefer capability-oriented structure over implementation-layer structure.
If the user asks to save it inside the active harness session, update .openarche/sessions/<plan-id>/state.json and keep the runbook structure valid.
If the user explicitly asks for a standalone document outside the live session, write it to the location they requested.
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 · 37 lines · 7 tokens per session scan A 28ce2b21b9ac
run is a command published in the GitHub repository Done-0/openarche (12 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 288 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.
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.