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 skills add FerroxLabs/ferrox-factory --skill ferrox-capturegit 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/skills/ferroxlabs/ferrox-factory/ferrox-capture)<a href="https://agentmods.dev/skills/ferroxlabs/ferrox-factory/ferrox-capture"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ferrox-factory/ferrox-capture.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.00025 | $0.00712 |
| Opus 5 | $0.00013 | $0.00356 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
ferrox-capture 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 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.
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.
What it actually says
Mode routing:
- default (no flag): Capture as a structured todo for later work → add-todo workflow
- --note: Zero-friction idea capture (append/list/promote) → note workflow
- --backlog: Add an idea to the backlog parking lot (999.x numbering) → add-backlog workflow
- --seed: Capture a forward-looking idea with trigger conditions → plant-seed workflow
- --list: List pending todos and select one to work on → check-todos workflow
- --list-seeds: List/audit captured seeds (optional status filter) → list-seeds workflow
| Flag | Destination | Workflow |
|---|---|---|
| (none) | Structured todo in .planning/todos/ | add-todo |
| --note | Timestamped note file, list, or promote | note |
| --backlog | ROADMAP.md backlog section (999.x) | add-backlog |
| --seed | .planning/seeds/SEED-NNN-slug.md | plant-seed |
| --list | Interactive todo browser + action router | check-todos |
| --list-seeds | Read-only seed list/audit (optional status filter) | list-seeds |
<execution_context>
@/.claude/ferrox-core/workflows/add-todo.md
@/.claude/ferrox-core/workflows/note.md
@/.claude/ferrox-core/workflows/add-backlog.md
@/.claude/ferrox-core/workflows/plant-seed.md
@/.claude/ferrox-core/workflows/check-todos.md
@/.claude/ferrox-core/workflows/list-seeds.md
@~/.claude/ferrox-core/references/ui-brand.md
</execution_context>
Parse the first token of $ARGUMENTS:
- If it is
--note: strip the flag, pass remainder to note workflow - If it is
--backlog: strip the flag, pass remainder to add-backlog workflow - If it is
--seed: strip the flag, pass remainder to plant-seed workflow - If it is
--list-seeds: strip the flag, pass remainder (optional status filter) to list-seeds workflow - If it is
--list: pass remainder (optional area filter) to check-todos workflow - Otherwise: pass all of $ARGUMENTS to add-todo workflow
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 · 68 lines · 25 tokens per session scan A ab3d0e4cc494
ferrox-capture is a skill published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 712 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.