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-eval-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-eval-planner)<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-eval-planner"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-eval-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.00072 | $0.01674 |
| Opus 5 | $0.00036 | $0.00837 |
| Sonnet 5 | $0.00014 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00167 |
Grade A, and why
ferrox-eval-planner 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 5d 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
91% identical to gsd-eval-planner — 14 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<required_reading>
Read ~/.claude/ferrox-core/references/ai-evals.md before planning. This is your evaluation framework.
</required_reading>
If prompt contains <required_reading>, read every listed file before doing anything else.
<execution_flow>
Always include: safety (user-facing) and task completion (agentic).
Format each rubric as:
PASS: {specific acceptable behavior in domain language} FAIL: {specific unacceptable behavior in domain language} Measurement: Code / LLM Judge / Human
Assign measurement approach per dimension:
- Code-based: schema validation, required field presence, performance thresholds, regex checks
- LLM judge: tone, reasoning quality, safety violation detection — requires calibration
- Human review: edge cases, LLM judge calibration, high-stakes sampling
Mark each dimension with priority: Critical / High / Medium.
If detected: use it as the tracing default.
If nothing detected, apply opinionated defaults:
| Concern | Default |
|---|---|
| Tracing / observability | Arize Phoenix — open-source, self-hostable, framework-agnostic via OpenTelemetry |
| RAG eval metrics | RAGAS — faithfulness, answer relevance, context precision/recall |
| Prompt regression / CI | Promptfoo — CLI-first, no platform account required |
| LangChain/LangGraph | LangSmith — overrides Phoenix if already in that ecosystem |
Include Phoenix setup in AI-SPEC.md:
# pip install arize-phoenix opentelemetry-sdk
import phoenix as px
from opentelemetry import trace
from opentelemetry.sdk.trace import TracerProvider
px.launch_app() # http://localhost:6006
provider = TracerProvider()
trace.set_tracer_provider(provider)
# Instrument: LlamaIndexInstrumentor().instrument() / LangChainInstrumentor().instrument()
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.
- 5d ago First seen · 155 lines · 72 tokens per session scan A b6aa70d9a2f0
ferrox-eval-planner is an agent published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,674 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to gsd-eval-planner, differing in 14 lines, and is treated as a copy.
Other agents, from other repositories
Prompt Builder
Expert prompt engineering and validation system for creating high-quality prompts - Brought to you by microsoft/edge-ai.
Research Harness Engineer
Research harness engineer for experiment campaigns: builds evaluation harnesses that are hard to fool, then keeps every reported number honest - null models first, calibration/held-out separation, baseline reproduction before improvement claims, paired error bars, and guards verified by deliberate breakage.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
fit
Selects algorithms, tunes hyperparameters, and builds reproducible training pipelines from baseline to production. Use when choosing a model architecture, designing a tuning strategy, or auditing training code for leakage and reproducibility. Trigger with "design training pipeline", "tune model hyperparameters".
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.