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/moira-mcp/moira/start-developmentgit clone --depth 1 https://github.com/moira-mcp/moiraWhat 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.00648 |
| Opus 5 | $0.00003 | $0.00324 |
| Sonnet 5 | $0.00001 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
start-development 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 3d 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
Start Development Workflow
Decide whether an update is needed: - If we are ON master → skip this stage (no need to rebase onto itself) - If on a feature/dev branch → check freshness relative to master
Check the branch is up to date: 1. Run git fetch origin to get fresh data 2. Update the local master: git -C <path-to-master-worktree> fetch origin master:master 3. Compare the current branch with master 4. Check whether there are uncommitted changes
Based on the check, decide: - If the branch is fresh → proceed to stage-1 - If master has new changes → suggest the user run /rebase-master - If there are uncommitted changes → ask what to do (commit/stash/continue)
Do not rebase if already on master
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.
- 3d ago First seen · 73 lines · 7 tokens per session scan A e74b88480e04
start-development is a command published in the GitHub repository moira-mcp/moira (21 stars, last pushed 3d ago), licensed Apache-2.0. It adds 7 tokens to every session and 648 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
team-plan
Assign roles to Agent teams for planning purposes given a user prompt.
deep-research
Deep research a topic using web search (Rube MCP) and multi-model consensus analysis (PAL MCP).
code-review
Code review git changes using multi-model consensus.
log-fix
Read Docker/installer logs and iteratively fix bugs based on log analysis.
tdd
Enforce strict TDD workflow - write test first, see it fail, then implement.
test-coverage
Identify and fill test gaps across Shell (BATS) and Python (pytest) test suites.