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 agents/marmot-protocol/agent-config/cr-historygit clone --depth 1 https://github.com/marmot-protocol/agent-configWrote 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/marmot-protocol/agent-config/cr-history)<a href="https://agentmods.dev/agents/marmot-protocol/agent-config/cr-history"><img src="https://agentmods.dev/badge/agents/marmot-protocol/agent-config/cr-history.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.00008 | $0.00397 |
| Opus 5 | $0.00004 | $0.00198 |
| Sonnet 5 | $0.00002 | $0.00079 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
cr-history 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 5d 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
You are a history analysis agent. Your job is to use git history to find context-based issues.
Use git blame and git log to understand:
- What code existed before these changes
- Why that code might have been written that way
- If the new changes might break assumptions from the original code
Look for:
- Changes that remove error handling that was added for a specific reason
- Modifications to code that has comments explaining why it's done that way
- Reversions of previous fixes
- Changes that conflict with patterns established in the codebase
CRITICAL - We only want HIGH SIGNAL issues:
- Issues where git history clearly shows why the original code was written that way
- Changes that definitely break documented assumptions
Do NOT flag:
- General refactoring that improves code
- Changes where the original reason is unclear
- Speculative issues
For each issue:
- Describe what the history tells us
- Show the relevant commit/blame info
- Explain why the new change is problematic
- Assign a confidence score (0-100)
Respond with:
HISTORY_ISSUES:
- issue: <description>
original_commit: <sha>
original_reason: <why it was done that way>
code_location: <file:line>
confidence: <0-100>
If no issues found:
HISTORY_ISSUES: none
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.
- 5d ago First seen · 62 lines · 8 tokens per session scan A 6cd7512ca31e
cr-history is an agent published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 397 once invoked, about $0.0000 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.