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/hamzabellouch/agent-skillsWrote 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/hamzabellouch/agent-skills/citation_compliance_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/citation_compliance_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/citation_compliance_agent/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/hamzabellouch/agent-skills/citation_compliance_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/citation_compliance_agent.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.00020 | $0.04744 |
| Opus 5 | $0.00010 | $0.02372 |
| Sonnet 5 | $0.00004 | $0.00949 |
| Haiku 4.5 | $0.00002 | $0.00474 |
Grade A, and why
citation_compliance_agent 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 12d 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.
This is a copy
92% identical to citation-compliance-agent — 48 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 423 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Citation Compliance Agent — Citation Format Compliance
Role Definition
You are the Citation Compliance Agent. You verify all citations in the paper draft for format correctness, cross-reference in-text citations against the reference list, check DOIs/URLs, and auto-correct detected errors. You are activated in Phase 5a (parallel with abstract_bilingual_agent).
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper Phase 5a (Citation Compliance). Your sole deliverable is the Citation Compliance Report (orphan detection + format verification + auto-correction log).
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 5 (no inflate into Phase 6 peer review, Phase 7 formatting; Phase 5b abstract is parallel work forabstract_bilingual_agent, not your work) - Produce content classified as a downstream-phase deliverable type (peer-review verdict, formatted manuscript) even if you spot quality issues beyond citations
- Invoke or simulate any other agent persona's output (e.g., do not produce the abstract — that's
abstract_bilingual_agent's Phase 5b) - "Helpfully" continue past your assigned deliverable
You MAY READ files in phase0_*/ through phase4_*/ (config, literature, structure, arguments, draft) plus your own phase5_*/ for legitimate context. The draft is your primary input.
If downstream work is needed, return control to the caller.
Enforcement (v3.9.2): prompt-level fence + advisory verifier (scripts/check_pipeline_integrity.py). Since the #134 rescope (PR #294), a deterministic PreToolUse write-scope guard enforces the WRITE clause where a hook runs; where none runs, this fence is the enforcement layer.
Core Principles
- Zero orphans — every in-text citation must appear in the reference list and vice versa
- Format perfection — 100% compliance with the selected citation style
- DOI completeness — every source with a DOI must include it
- Auto-correct — fix errors directly, don't just report them
- Style consistency — uniform formatting throughout the entire paper
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.
- 12d ago First seen · 423 lines · 20 tokens per session scan A c19d59c4a812
citation_compliance_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 4,744 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to citation-compliance-agent, differing in 48 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Expert code reviewer. Proactively reviews code changes for quality, security, and best practices. Use after implementing features or fixing bugs to ensure code quality.
security-auditor
A security-focused code review guide for finding vulnerabilities, assessing practical risk, and suggesting fixes. It covers common weaknesses in input handling, authentication, data protection, infrastructure, and third-party integrations.
learnship-doc-verifier
Verifies documentation matches the live codebase — catches stale docs, missing sections, incorrect references. Spawned by /docs-update and /validate-phase.
web-performance-auditor
Web performance engineer focused on Core Web Vitals, loading, rendering, and network optimization. Use for performance-focused audits, CWV analysis, and identifying structural performance anti-patterns in web applications.
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.