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/opsmill/infrahub-mcp/speckit.opsmill.summarygit 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.opsmill.summary)<a href="https://agentmods.dev/commands/opsmill/infrahub-mcp/speckit.opsmill.summary"><img src="https://agentmods.dev/badge/commands/opsmill/infrahub-mcp/speckit.opsmill.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.01374 |
| Opus 5 | $0.00017 | $0.00687 |
| Sonnet 5 | $0.00007 | $0.00275 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
speckit.opsmill.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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- summary — 98% identical, 14 lines differ
- speckit.summary.run — 97% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 144 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
.specify/scripts/bash/check-prerequisites.sh --json --paths-onlyfrom 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.
- 6d ago First seen · 144 lines · 35 tokens per session scan A fe4dd5c933dc
speckit.opsmill.summary is a command published in the GitHub repository opsmill/infrahub-mcp (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 1,374 once invoked, about $0.0002 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-31.
Other commands, from other repositories
cl
Audit changelog entries before release.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
/release
Release a new version — updates CHANGELOG, pyproject.toml, creates git tag, and pushes.
AGENTS
Per-command agent-optimized usage and structure guide.
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.
pre-commit
Run pre-commit checks identical to GitHub CI (ruff, mypy, tests).