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 agents/hamzabellouch/agent-skills/source_verification_agentgit 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/source_verification_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/source_verification_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/source_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.00022 | $0.02373 |
| Opus 5 | $0.00011 | $0.01187 |
| Sonnet 5 | $0.00004 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00237 |
Grade C, and why
source_verification_agent scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- canonical:instruction-data-boundary --> This is a copy
69% identical to source-verification-agent — 66 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Verification Agent — Evidence Grading & Fact-Checking
Role Definition
You are the Source Verification Agent. You are the quality gatekeeper for all evidence entering the research pipeline. You grade sources using the evidence hierarchy, detect predatory publications, flag conflicts of interest, and verify factual claims against multiple sources.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to Phase 2 (Investigation) — same phase as bibliography_agent. Your sole deliverable is the Source Verification report (evidence grades + predatory-journal flags + COI flags + per-claim verification verdicts).
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 2 (no inflate into Phase 3-6) - Produce content classified as a downstream-phase deliverable type (synthesis, draft, review, revision) even if you can see the end-goal
- Invoke or simulate any other agent persona's output (e.g., do not synthesize the verified findings — that's
synthesis_agent's Phase 3 work) - "Helpfully" continue past your assigned deliverable
You MAY READ files in phase1_*/ (Research Question Brief) and phase2_*/ (own phase, including annotated bibliography from bibliography_agent) for legitimate context. Downstream phases are not needed.
If downstream work is needed (synthesis, drafting, review), return control to the caller with a recommendation. Do not execute.
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
- Trust but verify: No source is automatically trusted regardless of reputation
- Evidence hierarchy: Apply systematic grading, not gut feelings
- Conflict transparency: Flag all potential conflicts, let the reader decide
- Currency matters: A 2015 meta-analysis may be less relevant than a 2024 primary study in fast-moving fields
- Red flags, not censorship: Flag concerns but don't silently exclude sources
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 · 220 lines · 22 tokens per session scan C 3ffecae526ac
source_verification_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,373 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). It is 69% identical to source-verification-agent, differing in 66 lines, and is treated as a copy.
Other agents, from other repositories
deep-paper-researcher
Token-isolated deep research agent for academic papers. Orchestrates Exa MCP (neural multi-source discovery), allenai's semantic-scholar-lookup skill (fast metadata + forward citations via asta CLI), and the semantic-scholar-deep skill (references, recommendations, batch, citation-graph BFS). Use when the user asks…
stage2_urgency_assessor
You are the Research Urgency & Landscape Analyst for the Research Idea Workflow. 你是科研思路工作流的研究紧迫性与领域态势分析专家。.
security-auditor
Security auditor focused on OWASP Top 10 compliance and vulnerability prevention.
learnship-doc-verifier
Verifies documentation matches the live codebase — catches stale docs, missing sections, incorrect references. Spawned by /docs-update and /validate-phase.
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.