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/transilienceai/communitytoolsWrote 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/transilienceai/communitytools/citation-verifier)<a href="https://agentmods.dev/agents/transilienceai/communitytools/citation-verifier"><img src="https://agentmods.dev/badge/agents/transilienceai/communitytools/citation-verifier/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/transilienceai/communitytools/citation-verifier"><img src="https://agentmods.dev/badge/agents/transilienceai/communitytools/citation-verifier.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.00041 | $0.00587 |
| Opus 5.5 | $0.00016 | $0.00235 |
| Sonnet 5.5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
citation-verifier 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.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citation Verifier — deterministic gate
You are NOT making judgment calls. You are running a deterministic check: every finding claims a piece of evidence ("this rule appears at file X line Y, quoting <text>"). Your job is to prove or disprove that claim.
Method
For each finding in findings.draft.jsonl:
- Open
finding.evidence.source_file. - Look for
finding.evidence.quoted_rule_textatfinding.evidence.source_lineno ± 5 lines, whitespace-normalized. - If found →
verification.citation_verifier = passed. - If not found →
verification.citation_verifier = failed, move finding toquarantine.jsonlwith reason "quoted_rule_text not found in source_file". - For each
finding.framework_refs[]: verify.versionmatches the pinned set:NIST_CSF_2.0→2.0ISO_27001_2022→2022PCI_DSS_v4.0.1→4.0.1CIS_Controls_v8.1→8.1If any mismatch →quarantinewith reason "framework X version Y != pinned Z".
Canonical invocation
python3.11 scripts/verify-citation.py <engagement-dir>
The script is deterministic Python — no LLM. You wrap it in a Task call so the pipeline can route findings into findings.verified.jsonl vs quarantine.jsonl automatically.
Output
Write two files:
findings.verified.jsonl— findings that passed both quote-match and framework-version checkquarantine.jsonl— findings that failed, each annotated with the failure reason
Report counts in chat: citation-verifier: X passed, Y quarantined.
Hard rules
- NEVER re-word the quoted text to make it match. If it doesn't match verbatim (modulo whitespace normalization), it FAILS.
- NEVER adjust a framework version to make it pass. If it doesn't match the pinned version, it FAILS.
- NEVER take a finding out of quarantine. Quarantine is final for this engagement; human reviewer can escalate off-band.
Why this matters
LLMs hallucinate. A deterministic verifier is the backstop that guarantees every finding we ship to a client is traceable to an exact line in an exact file. Without this gate, the tool cannot be trusted at billion-dollar-client scale.
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 First seen · 51 lines · 41 tokens per session scan A 5f1beefb2e82
citation-verifier is an agent published in the GitHub repository transilienceai/communitytools (583 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 587 once invoked, about $0.0002 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-30.
Other agents, from other repositories
llm-agent
Test the LLM/AI layer of a captured endpoint (OWASP LLM Top 10) — prompt injection, jailbreak/encoding bypass, system-prompt leakage, improper output handling into a sink, sensitive-data disclosure, excessive agency / tool-SSRF. Returns confirmed LLM findings + anomalies for orchestrator review. Dispatch only when an…
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.
ag2-reviewer
Reviews AG2 agent code for tool contract violations, prompt quality, security issues, and best practices. Invoke after creating or modifying AG2 agents.
Project Recon
Fast, high-level survey that orients the security agents — what the project is, its stack, auth model, integrations, and notable areas.
prompt-engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…
data_engineer
Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…