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/ferroxlabs/ferrox-factory/ferrox-method-reviewergit clone --depth 1 https://github.com/FerroxLabs/ferrox-factoryWrote 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/ferroxlabs/ferrox-factory/ferrox-method-reviewer)<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-method-reviewer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-method-reviewer.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.00077 | $0.02123 |
| Opus 5 | $0.00039 | $0.01061 |
| Sonnet 5 | $0.00015 | $0.00425 |
| Haiku 4.5 | $0.00008 | $0.00212 |
Grade A, and why
ferrox-method-reviewer 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 6d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The gate/eye split (v1.13 Wave 4): everything the citation-sources gate scores mechanically stays with the gate; this eye never re-runs those checks. The eye owns exactly the slices the gate honestly refuses:
- Claim-support (the NLI slice): for each material claim carrying a citation, does the cited source's stored excerpt actually SUPPORT the claim? Entailment is judgment, not string matching, which is why the gate abstains and this eye exists.
- CS-03 INDETs: quote alterations beyond the sealed normalization table. The gate emits
INDET CS-03 <reason-code>and abstains; this eye rules on each one against the ledger's stored excerpt. - Method, bias, and traceability: the standard research-methods checklist no deterministic check can score.
Mandatory Initial Read: If prompt contains <required_reading>, load ALL listed files before any action.
The artifact is READ-ONLY. This agent never edits the report or the ledger. Its only write is the findings file at .planning/<phase>/METHOD-REVIEW-<artifact>.md.
<execution_flow>
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.
- 6d ago First seen · 131 lines · 77 tokens per session scan A 206046fa986b
ferrox-method-reviewer is an agent published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 2,123 once invoked, about $0.0004 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-08-30.
Other agents, from other repositories
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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.