ferrox-project-researcher

ferrox-project-researcher is an agent for Claude Code, Codex from FerroxLabs/ferrox-factory. It costs 48 tokens per session (6,280 once invoked), scanned A, a copy of gsd-project-researcher, MIT.

A project research helper that studies the technology and product ecosystem around a project before a roadmap is made. A roadmap is a staged plan for what to build and in what order.

In plain words
What is it for?
Use it to research the stack, features, architecture, and pitfalls, then produce recommendations for project phases and areas needing deeper investigation.
Why use it?
Planning without understanding the surrounding tools, patterns, and risks can lead to poor technology choices or badly ordered work. This helper records research in files that later planning steps can use.

Agent for Claude CodeCodex

Written for Claude Code and Codex: PostToolUse hook event, but also reads ~/.codex or $CODEX_HOME. Also seen: reads .claude/ paths; mentions Codex; built for cline.

Part of the ferrox-core plugin — 81 skills, 42 agents, 7 hooks shipped together

Good fit Use it to research the stack, features, architecture, and pitfalls, then produce recommendations for project phases and areas needing deeper investigation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ferroxlabs/ferrox-factory/ferrox-project-researcher
Install

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.

Clone the repo
git clone --depth 1 https://github.com/FerroxLabs/ferrox-factory

Made for: Claude Code, Codex.

Or install ferrox-core, the plugin that ships this one along with the rest of its 81 skills, 42 agents, 7 hooks.

Wrote 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.

agentmods badge for ferrox-project-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher/github.svg)](https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher)
Your own site
<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher/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.

agentmods 80×15 button for ferrox-project-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-project-researcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,280 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.06280
Opus 5 $0.00024 $0.03140
Sonnet 5 $0.00010 $0.01256
Haiku 4.5 $0.00005 $0.00628

Measured 9d ago against content hash 2adfdc938a6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ferrox-project-researcher 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.

Origin

This is a copy

92% identical to gsd-project-researcher — 34 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.

agents/ferrox-project-researcher.md · 617 lines

How it starts

The opening of the file, as written. The whole thing — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Answer "What does this domain ecosystem look like?" Write research files in .planning/research/ that inform roadmap creation.

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.

Your files feed the roadmap:

File How Roadmap Uses It
SUMMARY.md Phase structure recommendations, ordering rationale
STACK.md Technology decisions for the project
FEATURES.md What to build in each phase
ARCHITECTURE.md System structure, component boundaries
PITFALLS.md What phases need deeper research flags

Be comprehensive but opinionated. "Use X because Y" not "Options are X, Y, Z."

@~/.claude/ferrox-core/references/untrusted-input-boundary.md

agent_skills: self-load per @~/.claude/ferrox-core/references/agent-skills-bootstrap.md

<documentation_lookup> @~/.claude/ferrox-core/references/research-documentation-lookup.md </documentation_lookup>

<research_modes>

Mode Trigger Scope Output Focus
Ecosystem (default) "What exists for X?" Libraries, frameworks, standard stack, SOTA vs deprecated Options list, popularity, when to use each
Feasibility "Can we do X?" Technical achievability, constraints, blockers, complexity YES/NO/MAYBE, required tech, limitations, risks
Comparison "Compare A vs B" Features, performance, DX, ecosystem Comparison matrix, recommendation, tradeoffs

</research_modes>

<tool_strategy>

Research Plan via Code Seam

The agent decides what to research (the questions). The seam decides which provider to use and manages caching.

Read the full file on GitHub · 617 lines

Changes

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.

  1. 9d ago First seen · 617 lines · 48 tokens per session scan A 2adfdc938a6b

Subscribe to this mod's changes

ferrox-project-researcher is an agent published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 6,280 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to gsd-project-researcher, differing in 34 lines, and is treated as a copy.