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/orin-dx/agent-pluginsWrote 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/agents/orin-dx/agent-plugins/commit-analyzer)<a href="https://agentmods.dev/agents/orin-dx/agent-plugins/commit-analyzer"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/commit-analyzer/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/agents/orin-dx/agent-plugins/commit-analyzer"><img src="https://agentmods.dev/badge/agents/orin-dx/agent-plugins/commit-analyzer.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.00137 | $0.00797 |
| Opus 5.5 | $0.00055 | $0.00319 |
| Sonnet 5.5 | $0.00027 | $0.00159 |
| Haiku 4.5 | $0.00014 | $0.00080 |
Grade A, and why
commit-analyzer 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 1mo 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
<load_first> shared/references/delivery/commits.md </load_first>
{
"commit_message": "string",
"type": "feat|fix|docs|style|refactor|test|chore|perf|ci|build",
"scope": "string|null",
"breaking": false,
"reasoning": "string"
}
reasoning is a scratchpad — explain how type and scope were chosen, in 1-2 sentences. It is not forwarded downstream, so a longer scratchpad buys nothing.
WHEN the change removes or alters a public API in a way that breaks existing callers, set breaking to true.
NEVER use the diff's file names or variable names as the commit message — explain the intent, not the mechanism.
IF scope cannot be determined from the diff alone, set it to null.
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.
- 1mo ago Changed · +1 lines c8955315ebc1
- 1mo ago First seen · 52 lines · 137 tokens per session scan A a92b5903049b
commit-analyzer is an agent published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed 18d ago), licensed MIT. It adds 137 tokens to every session and 797 once invoked, about $0.0005 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-31.
Other agents, from other repositories
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
mz-executor
Execute a single plan file with atomic commits per task.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
echo-developer
Echo Framework Developer. Implements code changes behind strict verification gates, runs automated tests, and creates atomic conventional commits.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.