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 skills add fedec65/bettercallclaude --skill citation-content-verifygit clone --depth 1 https://github.com/fedec65/bettercallclaudeWrote 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/skills/fedec65/bettercallclaude/citation-content-verify)<a href="https://agentmods.dev/skills/fedec65/bettercallclaude/citation-content-verify"><img src="https://agentmods.dev/badge/skills/fedec65/bettercallclaude/citation-content-verify/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/skills/fedec65/bettercallclaude/citation-content-verify"><img src="https://agentmods.dev/badge/skills/fedec65/bettercallclaude/citation-content-verify.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.00115 | $0.02827 |
| Opus 5 | $0.00057 | $0.01413 |
| Sonnet 5 | $0.00023 | $0.00565 |
| Haiku 4.5 | $0.00012 | $0.00283 |
Grade A, and why
citation-content-verify 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 Changed · +19 lines e6c59224b079
- 9d ago First seen · 161 lines · 115 tokens per session scan A 2c93d959e83d
citation-content-verify is a skill published in the GitHub repository fedec65/bettercallclaude (38 stars, last pushed 8d ago), licensed AGPL-3.0. It adds 115 tokens to every session and 2,827 once invoked, about $0.0006 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-30.
Other skills, from other repositories
verify
Run verification and code review on completed tasks.
review-plans
Review alignment between planning documents (PR/FAQ, PRDs, Tech Plans) and the codebase. Use when you want to detect drift, resolve conflicts, or ensure plans match reality.
codex-plan-apply
Apply a Codex-only Belmont planning handoff packet after a plan-mode product-plan or tech-plan interview; write only the explicit .belmont files named in the packet without asking new planning questions.
note
Save learnings and discoveries to NOTES.md for persistence across sessions.
reset
Reset belmont state files (PRD, PROGRESS, TECHPLAN) to start fresh.
debug-workflow
Systematically debug failing n8n workflows — expression errors, node type mismatches, pinned data issues, sub-workflow failures, authentication problems, rate limit errors, and silent data loss. Use this skill whenever the user reports an n8n workflow problem — phrases like "my n8n workflow is failing", "this…