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/opsmill/infrahub-mcpWrote 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/opsmill/infrahub-mcp/speckit.review)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.review"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.review.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.00026 | $0.01472 |
| Opus 5 | $0.00013 | $0.00736 |
| Sonnet 5 | $0.00005 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
speckit.review 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 8d 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.
This is a copy
89% identical to run — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive PR Review
Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality.
Review Aspects (optional): "$ARGUMENTS"
Review Workflow:
-
Load Configuration
- Read the project config file at
.specify/extensions/review/review-config.yml(if it exists). - If the file does not exist, fall back to the
defaults.agentssection in the extension'sextension.yml. - Extract the
agentsmap — each key (code,comments,tests,errors,types,simplify) is a boolean toggle. - Agents set to
falseMUST be excluded from this run. Do not launch them.
- Read the project config file at
-
Determine Review Scope
- Parse arguments to see if user requested specific review aspects.
- If specific aspects were requested, run exactly those — config toggles do not apply (explicit user request overrides config).
- Default (no arguments): Run all applicable reviews that are enabled in config.
-
Available Review Aspects:
- comments - Analyze code comment accuracy and maintainability
- tests - Review test coverage quality and completeness
- errors - Check error handling for silent failures
- types - Analyze type design and invariants (if new types added)
- code - General code review for project guidelines
- simplify - Simplify code for clarity and maintainability
- all - Run all applicable reviews (default)
-
Identify Changed Files
- If the user provided a file list or explicit instructions on how to retrieve files (e.g., only staged, only unstaged, a specific folder, etc.), follow those instructions directly.
- Otherwise, fall back to the default: execute the
.specify/scripts/bash/detect-changed-files.shwith--jsonto detect changed files.- The script automatically picks the best detection mode:
- Mode A (feature branch): diffs the current branch against the default branch (
main/master) from the merge-base, plus any staged and unstaged changes. - Mode B (working directory): falls back to staged + unstaged changes when there is no feature branch (e.g., working directly on the default branch).
- Mode A (feature branch): diffs the current branch against the default branch (
- JSON output:
{"branch", "default_branch", "mode", "changed_files": [...]}
- The script automatically picks the best detection mode:
- Note: The folder containing the script may be excluded from version control or hidden by search indexing.
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.
- 8d ago First seen · 178 lines · 26 tokens per session scan A e8e23abcb368
speckit.review is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 1,472 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to run, differing in 25 lines, and is treated as a copy.
Other commands, from other repositories
review
A guided command for reviewing code changes by examining the current Git diff, the record of edits between versions. It checks quality, bugs, security, performance, and maintainability.
council-sweep
Walk the configured watch paths and run Council on every artifact modified in the last N hours (default 24h).
council-review
Run the 5-agent Council on the current file or a specified path. Returns SHIP / REVISE / HOLD plus a revision brief.
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.