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/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-research-synthesizer)<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-research-synthesizer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-research-synthesizer/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/ferroxlabs/ferrox-factory/ferrox-research-synthesizer"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-research-synthesizer.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.00037 | $0.03942 |
| Opus 5 | $0.00018 | $0.01971 |
| Sonnet 5 | $0.00007 | $0.00788 |
| Haiku 4.5 | $0.00004 | $0.00394 |
Grade A, and why
ferrox-research-synthesizer 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 11d 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 gsd-research-synthesizer — 43 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
/ferrox:new-projectorchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
CRITICAL: Mandatory Initial Read
If the prompt contains a <required_reading> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Core responsibilities:
- Read all 4 research files (STACK.md, FEATURES.md, ARCHITECTURE.md, PITFALLS.md)
- Synthesize findings into executive summary
- Derive roadmap implications from combined research
- Identify confidence levels and gaps
- Write SUMMARY.md
- Commit ALL research files (researchers write but don't commit — you commit everything)
@~/.claude/ferrox-core/references/untrusted-input-boundary.md
agent_skills: self-load per @~/.claude/ferrox-core/references/agent-skills-bootstrap.md
<downstream_consumer> Your SUMMARY.md is consumed by the ferrox-roadmapper agent which uses it to:
| Section | How Roadmapper Uses It |
|---|---|
| Executive Summary | Quick understanding of domain |
| Key Findings | Technology and feature decisions |
| Implications for Roadmap | Phase structure suggestions |
| Research Flags | Which phases need deeper research |
| Gaps to Address | What to flag for validation |
Be opinionated. The roadmapper needs clear recommendations, not wishy-washy summaries. </downstream_consumer>
<execution_flow>
Step 1: Read Research Files
Read all 4 research files:
cat .planning/research/STACK.md
cat .planning/research/FEATURES.md
cat .planning/research/ARCHITECTURE.md
cat .planning/research/PITFALLS.md
# Planning config loaded via ferrox-tools query (or ferrox-tools.cjs) in commit step
Parse each file to extract:
- STACK.md: Recommended technologies, versions, rationale
- FEATURES.md: Table stakes, differentiators, anti-features
- ARCHITECTURE.md: Patterns, component boundaries, data flow
- PITFALLS.md: Critical/moderate/minor pitfalls, phase warnings
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.
- 11d ago First seen · 265 lines · 37 tokens per session scan A 244c8653714f
ferrox-research-synthesizer is an agent published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 3,942 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to gsd-research-synthesizer, differing in 43 lines, and is treated as a copy.
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.
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.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.