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/summary)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/summary"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/summary.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.00035 | $0.01334 |
| Opus 5 | $0.00017 | $0.00667 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
summary 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.
This is a copy
98% identical to speckit.opsmill.summary — 14 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Supported argument: --since <commit|time> to bound the summary window.
Examples:
--since HEAD~10— limit the timeline to phases that began after the 10th-most-recent commit on this branch.--since 14:00— only include phases that occurred after 2 PM local time in the active session.
If no argument is given, summarize the entire live session.
Goal
Produce a single markdown document that lets a teammate (or future-you)
understand the flow of the session in under 60 seconds. The unit of
output is the working session, not any one artifact. Different
granularity from speckit.archive (per-feature, permanent) and
speckit.reconcile.run (drift-fixing).
Operating Constraints
STAY AT THE FLOW LEVEL. This summary is a narrative, not a transcript. Do NOT include any of the following:
- Per-tool-call narration ("called Read on X.py, then called Edit on...")
- Diffs or hunks of any size
- Line numbers
- Code snippets longer than a single line
- File-by-file change logs (those belong in PR descriptions and
git log) - Step-by-step reproductions of debugging
- Quotes from the conversation buffer longer than one short clause
STRICTLY ADDITIVE. Do not modify spec.md, plan.md, tasks.md,
or any source files. The only file this command writes is the session
summary itself.
IDEMPOTENT IN SPIRIT. A second invocation in the same session must produce a comparable summary, not a summary of summaries. Ignore previously generated session files when composing the new one.
Outline
-
Run
{SCRIPT}from repo root and parseFEATURE_DIRfrom the JSON output. All paths must be absolute.- If
FEATURE_DIRis missing, empty, or the resolved directory does not exist, fail fast with a clear error such as:No feature directory resolved from current branch — /speckit.opsmill.summary requires an active feature branch.Suggest the user switch to a feature branch and re-run.
- If
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 · 140 lines · 35 tokens per session scan A ae773610b3bc
summary is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,334 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to speckit.opsmill.summary, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
hep-graph.body
A command for viewing saved Agentlas automation graphs and requesting that one be run. The desktop app performs the actual run.
fire-execute-plan
Execute a single plan with segment-based routing, per-task atomic commits, and test enforcement.
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
tree
Emit a compact indented view of the active task hierarchy and refresh state/task-tree.json. This is the primary tool for understanding the board's shape before adding new work.
pm-review-user-01-happy
Un PRD est disponible dans output/. Le wiki contient des pages persona- et interview- avec des verbatims. Le pm-user-advocate vérifie l'alignement du PRD avec les personas, identifie les personas non servis, cite les verbatims contradictoires, et évalue le niveau de confiance de chaque claim. Une page type…
create-story
Create the next user story from epics+stories with enhanced context analysis and direct ready-for-dev marking.