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 skills/addyosmani/factory/factory-triagenpx skills add addyosmani/factory --skill factory-triagegit clone --depth 1 https://github.com/addyosmani/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/addyosmani/factory/factory-triage)<a href="https://agentmods.dev/skills/addyosmani/factory/factory-triage"><img src="https://agentmods.dev/badge/skills/addyosmani/factory/factory-triage.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.00036 | $0.00121 |
| Opus 5 | $0.00018 | $0.00060 |
| Sonnet 5 | $0.00007 | $0.00024 |
| Haiku 4.5 | $0.00004 | $0.00012 |
Grade A, and why
factory-triage 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 6d 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
Factory triage for Codex
Read docs/factory/CONTRACT.md, docs/factory/CHARTER.md, and then the canonical workflow
in .claude/skills/factory-triage/SKILL.md. Follow that workflow using the tools available
in Codex. GitHub labels are the live queue; QUEUE.md is only a snapshot.
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.
- 6d ago First seen · 12 lines · 36 tokens per session scan A ba87803d4a12
factory-triage is a skill published in the GitHub repository addyosmani/factory (174 stars, last pushed 15d ago), licensed MIT. It adds 36 tokens to every session and 121 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
agentic-code-review
Use to review a diff against repository contracts, specs, docs, tests, and architecture boundaries.
mcp-tool-policy-review
Use when adding, changing, or reviewing MCP servers, agent tools, provider integrations, credentials, scopes, or tool approval behavior.
spec-to-plan
Use when converting a product spec, use case, or PRD into a concrete implementation plan before code changes.
subagent-supervisor
Use when splitting complex work into independent subagent tasks with clear ownership, evidence, and integration responsibilities.
tdd-implementation-loop
Use when implementing behavior from an approved plan with test-first or regression-test-first development.
factory-retrospective
Use after incidents, regressions, repeated review findings, or completed features to convert lessons into durable factory improvements.