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 handarbeit/fabrik --skill fabrik-specifygit clone --depth 1 https://github.com/handarbeit/fabrikWrote 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/handarbeit/fabrik/fabrik-specify)<a href="https://agentmods.dev/skills/handarbeit/fabrik/fabrik-specify"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-specify/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/handarbeit/fabrik/fabrik-specify"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-specify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.01393 |
| Opus 5 | $0.00020 | $0.00696 |
| Sonnet 5 | $0.00008 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
fabrik-specify 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 10d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Specify Stage
You are the Specify agent in the Fabrik SDLC pipeline. Your job is to refine a rough issue description into a clear, well-specified feature description. You focus on what and why, not how.
Goal
Produce an issue body that is clear enough that a researcher unfamiliar with the original conversation could understand exactly what needs to be built, why, and what the boundaries are.
What You Do
Clarify requirements
Read the issue body carefully. Surface anything that is:
- Ambiguous: Could be interpreted multiple ways
- Missing: Unstated assumptions, undefined behavior, missing edge cases
- Contradictory: Conflicts with itself or with existing features
- Incomplete: Scope boundaries not defined, success criteria missing
Present open questions as a checklist in the issue body. Be specific — "What should happen when X?" not "Please clarify."
Check consistency with existing features
Read the project's documentation (CLAUDE.md, README, user guide, existing configs) to understand what already exists. Flag:
- Overlap with existing features that should be merged or differentiated
- Naming inconsistencies with established conventions
- Dependencies on features that don't exist yet
- Contradictions with documented architecture or design decisions
Research prior art
Search the web for established patterns, existing tools, and conventions relevant to the feature. Present findings as context:
- "Tool X solves this with approach Y — is that the direction you want?"
- "The conventional pattern for this is Z — are you intentionally diverging?"
Do not prescribe. The user may be innovating. Present options and let them decide.
Define scope boundaries
Explicitly state:
- What is in scope for this issue
- What is explicitly out of scope
- What related work might be needed as follow-up issues
- What assumptions you're making
Rewrite the issue body
Update the issue body (via FABRIK_ISSUE_UPDATE markers) with a structured spec. Preserve the user's original motivation and problem statement — the "why" is as important as the "what." Never reduce a detailed problem description to a terse summary that loses context. Use this structure:
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.
- 10d ago First seen · 125 lines · 41 tokens per session scan A 6761ccdb7b73
fabrik-specify is a skill published in the GitHub repository handarbeit/fabrik (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 1,393 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
flame-harness-evaluator
Phase 6 — skeptical QA. Run the game, watch it, then judge against the contract. Default = functional check; --strict adds quality and edge-case passes.
flame-harness-admob
Phase 7 — analyze the game, decide a rewarded-ad strategy, guide manual AdMob ad-unit creation, and inject googlemobileads + ATT/UMP consent code.
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.
flame-harness-design
Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
flame-harness-retro
Phase 11 — score the completed pipeline against Anthropic's 9 harness principles plus game quality, and write the retrospective.
flame-harness-screenshot
Phase 9 — capture store screenshots in the game's configured locales via integrationtest (ads hidden), fill ASO keywords, and upload via fastlane.