Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/samibs/skillfoundry/mission)<a href="https://agentmods.dev/commands/samibs/skillfoundry/mission"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/mission.svg" alt="Measured on agentmods" 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.00132 | $0.01252 |
| Opus 5 | $0.00066 | $0.00626 |
| Sonnet 5 | $0.00026 | $0.00250 |
| Haiku 4.5 | $0.00013 | $0.00125 |
Grade A, and why
mission 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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mission — Governed Development Mission Protocol
Implement → Test → Iterate → Validate → Evidence → Integrate → Publish
Full protocol:
MULTI_AGENT_PROTOCOL.md· Agent module:agents/_governed-mission-protocol.md
A change is not complete because it compiles, tests locally, or has a commit. Completion requires traceability, evidence, provenance, clean termination, and acceptance.
/mission writes machine-readable artifacts under .ai/ that outlive the agent that produced
them. You do not hand-write that JSON — the CLI writes and validates it, and refuses claims
the repository cannot substantiate.
What it prevents
| Failure | How /mission blocks it |
|---|---|
| Two agents writing in one directory | Registration refuses a second ACTIVE write agent per worktree. |
| A "worktree" that is really a copied folder | Verified against git worktree list --porcelain. |
| "Tests pass" while the runner hung | normal_termination and orphan detection; reported NOT CLEAN. |
| A dev server orphaned after the run | Ownership registry + identity-verified targeted cleanup. |
| A contribution silently dropped in a merge | Provenance: LOST/UNKNOWN block acceptance. Pass --base so a multi-commit contribution is verified as one range. |
| "Pushed" ≠ published | publish-check re-reads the remote SHA, tree and content. |
| "Probably pre-existing" | Requires a baseline run at the accepted SHA, or it is not substantiated. |
| Retry loops burning budget | NO_PROGRESS after two identical failures with no state change. |
| A ledger that drifts from reality | /mission reconcile — the ledger is corrected, never reality. |
Single-worker flow
/mission init STORY-042 --title "JWT refresh rotation"
/mission attest STORY-042 --worker claude-coder-042 --agent claude --allow-main
/mission gate STORY-042 # WRITES AUTHORIZED / BLOCKED
# ... implement ...
/mission evidence STORY-042 --kind tests --run "npm test"
/mission ac STORY-042 --file criteria.json
git commit -m "feat(auth): refresh rotation [STORY-042]"
/mission commit STORY-042 --base <base-sha> # a contribution is usually >1 commit
/mission set STORY-042 implementation_status COMPLETE
/mission set STORY-042 acceptance_status PASS
/mission verify STORY-042
/mission report STORY-042 --out docs/reports/STORY-042.md
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.
- today First seen · 111 lines · 132 tokens per session scan A 25b88d8245f3
mission is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed yesterday), licensed MIT. It adds 132 tokens to every session and 1,252 once invoked, about $0.0007 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-09-05.
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.