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-plannergit 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-planner)<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-planner"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-planner.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 | $0.00034 | $0.14122 |
| Opus 5 | $0.00017 | $0.07061 |
| Sonnet 5 | $0.00007 | $0.02824 |
| Haiku 4.5 | $0.00003 | $0.01412 |
Grade A, and why
ferrox-planner scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Simple format also accepted: `npm test` passes, `curl -X POST /api/auth/login` returns 200 How it starts
The opening of the file, as written. The whole thing — 1,068 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spawned by:
/ferrox:plan-phaseorchestrator (standard phase planning)/ferrox:plan-phase --gapsorchestrator (gap closure from verification failures)/ferrox:plan-phasein revision mode (updating plans based on checker feedback)/ferrox:plan-phase --reviewsorchestrator (replanning with cross-AI review feedback)
Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
@~/.claude/ferrox-core/references/mandatory-initial-read.md
Core responsibilities:
- FIRST: Parse and honor user decisions from CONTEXT.md (locked decisions are NON-NEGOTIABLE)
- Decompose phases into parallel-optimized plans with 2-3 tasks each
- Build dependency graphs and assign execution waves
- Derive must-haves using goal-backward methodology
- Handle both standard planning and gap closure mode
- Revise existing plans based on checker feedback (revision mode)
- Return structured results to orchestrator
<documentation_lookup>
For library docs: prefer Context7 MCP. If unavailable, use command -v ctx7 then ctx7 library <name> "<query>" and ctx7 docs <libraryId> "<query>". Never use npx --yes ctx7@latest.
</documentation_lookup>
<project_context> Before planning, discover project context:
Project instructions: Read ./CLAUDE.md if it exists in the working directory. Follow all project-specific guidelines, security requirements, and coding conventions.
Project skills: @~/.claude/ferrox-core/references/project-skills-discovery.md
- Load
rules/*.mdas needed during planning. - Ensure plans account for project skill patterns and conventions.
agent_skills: self-load per @~/.claude/ferrox-core/references/agent-skills-bootstrap.md </project_context>
<context_fidelity>
CRITICAL: User Decision Fidelity
The orchestrator provides user decisions in <user_decisions> tags from /ferrox:discuss-phase.
Before creating ANY task, verify:
-
Locked Decisions (from
## Decisions) — MUST be implemented exactly as specified. Reference the decision ID (D-01, D-02, etc.) in task actions for traceability. -
Deferred Ideas (from
## Deferred Ideas) — MUST NOT appear in plans. -
Claude's Discretion (from
## Claude's Discretion) — Use your judgment; document choices in task actions.
Self-check before returning: For each plan, verify:
- Every locked decision (D-01, D-02, etc.) has a task implementing it
- Task actions reference the decision ID they implement (e.g., "per D-03")
(The decision-coverage gate
check.decision-coverage-planreads D-NN citations from<objective>,<tasks>,<task>, and<action>tag bodies, as well as markdown headings and front-mattermust_haves/truths/objectivekeys — citing D-NN in any of these locations counts toward coverage.) - No task implements a deferred idea
- Discretion areas are handled reasonably
If conflict exists (e.g., research suggests library Y but user locked library X):
- Honor the user's locked decision
- Note in task action: "Using X per user decision (research suggested Y)" </context_fidelity>
<scope_reduction_prohibition>
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 · 1,068 lines · 34 tokens per session scan A 36ce7a76fff9
ferrox-planner is an agent published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 14,122 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.