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.
git clone --depth 1 https://github.com/moira-mcp/moiraWrote 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/moira-mcp/moira/finish-feature)<a href="https://agentmods.dev/commands/moira-mcp/moira/finish-feature"><img src="https://agentmods.dev/badge/commands/moira-mcp/moira/finish-feature/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/moira-mcp/moira/finish-feature"><img src="https://agentmods.dev/badge/commands/moira-mcp/moira/finish-feature.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.00268 |
| Opus 5.5 | $0.00004 | $0.00107 |
| Sonnet 5.5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
finish-feature 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 16d 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
Finish feature
Check whether the current development workflow already owns the requested remaining work. Continue that lifecycle when applicable; do not split implementation, tests, documentation or review into another run merely because this command exists.
For an intended separate completion task, discover available workflows through the configured
Moira list tool and select the exact authorized completion identity. The completion catalog can
be private; this public command does not install it or grant access. If no matching flow exists,
report the available choices without substituting an unrelated workflow or inventing an owner.
Follow the Agent Guide:
start first prepares the selected workflow and explicit intended parent (or "none"), then
executes the exact returned startAttemptId. Collect the same attempt after a lost execute reply;
do not prepare a replacement. Preserve the process identity in the project's locally ignored
agent workspace and continue with each current Step attempt only after completing its real work.
Use current exposed tool names, not retired aliases. $ARGUMENTS provides the feature/task context.
The selected workflow and user's authorization determine Git, publication and deployment effects;
this prompt grants no additional effects or permission to bypass repository protection.
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.
- 16d ago Changed · -25 lines · +2 tokens per session 134d50fd28eb
- 2mo ago First seen · 50 lines · 7 tokens per session scan A 467949a8ea61
finish-feature is a command published in the GitHub repository moira-mcp/moira (126 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 268 once invoked, about $0.0000 per session on Opus 5.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.
finish-feature compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| finish-featuremoira-mcp/moira | Command | 126 | 5d ago | Apache-2.0 | A | 9 | Claude Code |
| save-to-mdjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | A | 9 | Claude Code |
| checkjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | A | 10 | Claude Code |
| deployjmagar/claude-homelab | Command | 87 | 1mo ago | MIT | B | 14 | Claude Code |
| checklistgithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 149k | today | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 149k | today | MIT | A | 13 | Claude Code |