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-using-skillsgit 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-using-skills)<a href="https://agentmods.dev/skills/ferroxlabs/ferrox-factory/ferrox-using-skills"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ferrox-factory/ferrox-using-skills/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/skills/ferroxlabs/ferrox-factory/ferrox-using-skills"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ferrox-factory/ferrox-using-skills.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.00000 | $0.00912 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
ferrox-using-skills 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted from Superpowers using-superpowers by Obra (MIT) — see NOTICE.
This is the fork's single skill-invocation mandate. It is the ONLY skill that carries the <!-- ferrox:skill-invocation-mandate --> marker; no discipline skill carries it.
The Rule
If there is even a real chance a skill applies to what you are about to do, you MUST invoke it before responding or acting — including before clarifying questions, exploring the codebase, or reading files. If the skill turns out to be wrong for the situation, you don't have to follow it, but you check first.
Then announce "Using [skill] to [purpose]" and follow the skill exactly. If it has a checklist, create a todo per item.
This is not negotiable. You cannot rationalize your way out of checking.
The Ferrox Surfacing Model
Ferrox Factory pairs a context-engineered lifecycle spine with Superpowers' per-task discipline as the floor. Two layers, both surfaced through this one mandate:
- Macro flow: the Ferrox lifecycle skills own the shape of the work: discuss → plan → execute → verify (plus the phase/milestone/audit machinery). Route project-level intent through these; do not invent a competing process vocabulary.
- Micro-discipline floor — the vendored Ferrox disciplines are the quality floor inside a task:
ferrox-test-driven-development— before writing implementation code for any feature or bugfix.ferrox-systematic-debugging— before proposing a fix for any bug, test failure, or unexpected behavior.ferrox-verification-before-completion— before claiming work is complete, fixed, or passing; evidence before assertions, always.ferrox-requesting-code-review— when completing tasks or major features, before merging.ferrox-receiving-code-review— when acting on review feedback, before implementing suggestions.
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.
- 9d ago First seen · 65 lines · 0 tokens per session scan A c5242f0abe46
ferrox-using-skills is a skill published in the GitHub repository FerroxLabs/ferrox-factory (22 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 912 tokens. 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-08-30.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.