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/maintaingit 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.00011 | $0.00281 |
| Opus 5 | $0.00005 | $0.00140 |
| Sonnet 5 | $0.00002 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
maintain 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 or update the maintenance stage for the current harness session.
Required behavior:
- Prefer the current session state in
.openarche/sessions/<task-id>/state.json. Only create a separate note when the user explicitly asks for one. - Read the current
runbook.maintenance.specsection and keep its existing structure stable. - Use
runbook.maintenance.specas the source of truth for:qualitySweepdriftSweepcleanupTasksknowledgeCaptureknowledgeCaptureSummaryfollowupsRecordedblockersready
- If you update maintenance state, write it back into the session state and keep the full file valid.
- If the task is tied to a harness session, prefer updating the real session state over writing free-form prose.
When presenting maintenance work, organize it into:
- cleanup tasks already recorded
- whether knowledge capture is still pending, queued, captured, failed, or not applicable
- whether follow-ups are fully recorded
- what blockers still keep the maintenance stage open
Do not invent maintenance tasks outside the current spec unless the user explicitly asks to add them.
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 · 33 lines · 11 tokens per session scan A 472a47234521
maintain is a command published in the GitHub repository Done-0/openarche (12 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 281 once invoked, about $0.0001 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.