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/bengous/claude-code-plugins/fact-check-codegit clone --depth 1 https://github.com/bengous/claude-code-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/commands/bengous/claude-code-plugins/fact-check-code)<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/fact-check-code"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/fact-check-code.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.00013 | $0.00458 |
| Opus 5 | $0.00006 | $0.00229 |
| Sonnet 5 | $0.00003 | $0.00092 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
fact-check-code 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact Check (Code)
Verify the following claim about this codebase:
Process
- Search the codebase - Use Grep and Glob in parallel to find relevant files and patterns
- Read and verify - Examine the actual implementation, not just file names or comments
- Consult external sources - Use WebSearch/WebFetch if the claim involves library behavior or standards
- Report - Present findings with specific file references
<parallel_search_guidance> Run multiple searches in parallel: search for the claimed behavior, related function/class names, and configuration files simultaneously. Check multiple potential locations since code organization varies. </parallel_search_guidance>
Output Format
Verdict
<verdict_definitions>
- Confirmed: Code evidence directly supports the claim
- Partially True: Claim is accurate in some aspects but incomplete or contains inaccuracies
- Incorrect: Code evidence contradicts the claim
- Unable to Verify: Relevant code not found, or evidence is inconclusive </verdict_definitions>
Evidence
- Cite specific files and line numbers:
path/to/file.ts:42 - Quote relevant code snippets when helpful
- Explain discrepancies between claim and actual implementation
Sources
- List files examined with line references
- Include web sources if consulted for library/API behavior
Guidelines
- Always search before concluding - never rely on assumptions or prior knowledge
- Check multiple locations using different search terms (the code might use unexpected naming)
- Distinguish "not found after thorough search" from "confirmed absent" - explain your search strategy
- State your interpretation if the claim is ambiguous before searching
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.
- 2d ago First seen · 62 lines · 13 tokens per session scan A 8ab5616f361b
fact-check-code is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 458 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
root-cause
Use when any test fails, bug appears, or behaviour surprises you, before proposing a fix - find the cause and prove it, by reading real evidence, tracing bad values back to their origin, comparing against a working case, and testing one hypothesis at a time.
verify-loop
자동 재검증 루프 (최대 3회 재시도, 실패 시 자동 수정).
build-fix
빌드 에러를 자동으로 분석하고 수정합니다.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
branch-review
Command "branch-review" from hamr0/agentic-toolkit, covering guardrails, target — check the tree first, then interpret $arguments, effort level, stage 1 — general review and stage 2 — security (always full).
mcp-builder
Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).