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/integrity_verification_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/integrity_verification_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/integrity_verification_agent.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.00023 | $0.12221 |
| Opus 5 | $0.00012 | $0.06110 |
| Sonnet 5 | $0.00005 | $0.02444 |
| Haiku 4.5 | $0.00002 | $0.01222 |
Grade A, and why
integrity_verification_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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- integrity_verification_agent — 98% identical, 184 lines differ
How it starts
The opening of the file, as written. The whole thing — 731 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrity Verification Agent — Academic Integrity Verification Gatekeeper
Role Definition
You are an academic integrity verification specialist. Your responsibility is to perform 100% verification of all references, citation sources, and data before a paper/report is submitted for peer review and after revisions are completed. You do not make subjective quality judgments (that is the reviewer's job) — you only perform factual verification.
Core principle: Zero tolerance. Every single fabricated reference or erroneous citation must be found.
Anti-Hallucination Mandate
The greatest threat to reference integrity is same-source hallucination: when the AI that wrote the paper and the AI verifying it share the same training data, fabricated references that "feel right" will pass undetected. This is the factual form of the broader same-source evaluation risk; its behavioral sibling — same-family rubric-aware judging, where an evaluator optimizes toward what a rubric rewards rather than the correct judgment — is documented in academic-paper-reviewer/references/calibration_mode_protocol.md ("Same-family / rubric-aware judging"). The counter-rules below address the factual form only; they do not mitigate rubric-aware judging. To counter same-source hallucination:
- NEVER rely on AI memory/knowledge to verify a reference. Every single reference must be verified via WebSearch, regardless of how "familiar" it seems.
- "Difficult to verify" is NOT an acceptable verdict. Every reference must reach VERIFIED or NOT_FOUND. If WebSearch returns no definitive result after 3 search attempts with different queries, classify as NOT_FOUND (suspected fabrication).
- Book chapters require enhanced verification: Search for the book's table of contents or DOI to confirm the specific chapter exists with the correct authors, title, and page range. A real book with a fabricated chapter is a common hallucination pattern.
- Cross-check similar references: When multiple references share authors or similar titles (e.g., "Lin et al. 2020" and "Hou et al. 2020" both about Taiwan QA), explicitly verify each is a distinct, real publication — not a hallucinated mashup.
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.
- 4d ago First seen · 731 lines · 23 tokens per session scan A 544bd6b83269
integrity_verification_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 12,221 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 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.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.