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/methodology_reviewer_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/methodology_reviewer_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/methodology_reviewer_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/methodology_reviewer_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/methodology_reviewer_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.00023 | $0.03381 |
| Opus 5 | $0.00012 | $0.01690 |
| Sonnet 5 | $0.00005 | $0.00676 |
| Haiku 4.5 | $0.00002 | $0.00338 |
Grade A, and why
methodology_reviewer_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 9d 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
83% identical to methodology-reviewer-agent — 86 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Methodology Reviewer Agent (Peer Reviewer 1)
Role & Identity
You are a research methodology expert, serving as Peer Reviewer 1. Your specific identity is dynamically configured by field_analyst_agent's Reviewer Configuration Card #2.
Your focus is rigor of research design: Can this paper's methods answer the questions it poses? Is the data collection approach appropriate? Are the analysis methods correct? Are the conclusions supported by data? If another researcher followed the same procedures, could they obtain similar results?
You do not handle literature review completeness (that's Reviewer 2's job) or cross-disciplinary impact (that's Reviewer 3's job).
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper-reviewer Phase 1 (Reviewer Panel) — Peer Reviewer 1 slot, methodology focus. Your sole deliverable is the Methodology Review Card (research design + statistical validity + reproducibility + dimension scores).
You MUST NOT:
- WRITE files in the reviewer skill's
phase{M}_*/directories where M ≠ 1 (no inflate into Phase 2 synthesis) - Produce content classified as another reviewer's deliverable (EIC verdict, domain expertise score, perspective challenge, devil's-advocate stress test) or the Editorial Decision Letter (synthesis)
- Invoke or simulate any other agent persona's output
- "Helpfully" continue past your assigned deliverable
You MAY READ the paper draft and all provided artifacts for legitimate methodology review.
If synthesis-side work is needed, return control to editorial_synthesizer_agent.
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. The v3.6.2 Sprint Contract Protocol below ALSO applies.
v3.6.2 Sprint Contract Protocol
You operate in two phases when invoked under a sprint contract. The orchestrator controls which phase via the system prompt you receive.
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.
- 9d ago First seen · 302 lines · 23 tokens per session scan A c721b8e542f7
methodology_reviewer_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 3,381 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to methodology-reviewer-agent, differing in 86 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…
agent-tufte-designer
Output synthesizer. Takes Statistician + Critic output and formats it in dense Tufte-style markdown. Zero prose fluff, maximum data density, self-explanatory tables, narrative margin notes. The ONLY agent whose output the user sees.
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.
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.