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/fabriqaai/specs.md/flamenpx skills add fabriqaai/specs.md --skill flamegit clone --depth 1 https://github.com/fabriqaai/specs.mdWrote 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/fabriqaai/specs.md/flame)<a href="https://agentmods.dev/skills/fabriqaai/specs.md/flame"><img src="https://agentmods.dev/badge/skills/fabriqaai/specs.md/flame.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 | $0.00025 | $0.01427 |
| Opus 5 | $0.00013 | $0.00714 |
| Sonnet 5 | $0.00005 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
flame 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<degrees_of_freedom> MEDIUM — Structured evaluation with room for user input and collaborative extension. </degrees_of_freedom>
| Hat | Perspective |
|-----|------------|
| White (Facts) | What do we know? What data exists? |
| Yellow (Benefits) | What's the best case? Why could this work? |
| Black (Risks) | What could go wrong? What are the dangers? |
| Green (Creative) | How could this be extended or combined? |
| Blue (Process) | What would it take to implement? What's the path? |
</format>
<critical>Red Hat is handled separately in step 3 — it requires user input</critical>
<action>Present analysis in batches of 3-5 ideas to avoid overwhelming</action>
**Feasibility** (1-5): How achievable is this?
- 5: Easy — could start today with existing resources
- 4: Doable — requires some effort but clearly achievable
- 3: Challenging — significant effort but realistic
- 2: Hard — requires major investment or breakthroughs
- 1: Near-impossible — fundamental barriers exist
</scoring>
<action>Present as a 2x2 matrix view: high-impact/high-feasibility quadrant first</action>
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 133 lines · 25 tokens per session scan A a020aba6ce8b
flame is a skill published in the GitHub repository fabriqaai/specs.md (205 stars, last pushed 11d ago), licensed MIT. It adds 25 tokens to every session and 1,427 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-08-30.
Other skills, from other repositories
acceptance-orchestrator-v2
Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files…
acceptance-orchestrator
Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files…
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
testing-skill
Record, rewrite, and debug VCR cassettes for HTTP recordings. Use when running tests with --record-mode, verifying cassette playback, or inspecting request/response bodies in YAML cassettes.
agent-session-monitor
Real-time agent conversation monitoring - monitors Higress access logs, aggregates conversations by session, tracks token usage. Supports web interface for viewing complete conversation history and costs. Use when users ask about current session token consumption, conversation history, or cost statistics.