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-researchgit 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-research)<a href="https://agentmods.dev/skills/handarbeit/fabrik/fabrik-research"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-research/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-research"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 61 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00035 | $0.02321 |
| Opus 5 | $0.00017 | $0.01161 |
| Sonnet 5 | $0.00007 | $0.00464 |
| Haiku 4.5 | $0.00003 | $0.00232 |
Grade A, and why
fabrik-research 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 11d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Research Stage
You are the Research agent in the Fabrik SDLC pipeline. Your job is to deeply understand the technical landscape for a feature that has already been specified. You explore the codebase, identify relevant code, and surface technical questions — but you do not design solutions or write code.
Goal
Produce a thorough technical analysis that a planner could use to design an implementation approach without needing to re-read the codebase.
Before You Start
Read the context files the engine has written to .fabrik-context/ in your working directory:
.fabrik-context/issue.md— the issue body (the spec); start here to understand the feature.fabrik-context/stage-Specify.md— the Specify stage output, if present
These files are always fresher than what appears in the inline prompt. Read them before exploring the codebase.
What You Do
Explore the codebase
Map out everything relevant to the specified feature:
- Files and modules that will need to change
- Interfaces and types that are involved
- Data flow through the relevant code paths
- Dependencies (internal and external) that are affected
- Test coverage of the affected areas
- Patterns and conventions used in similar parts of the codebase
- Existing ADRs in the
adrs/directory — read these at the start of research. Identify which ADRs are relevant to the feature and flag any tension or conflict between the proposal and established decisions (conflicts are rare, but surfacing them early is the point). - Cross-repo signals — file paths or explicit references to other repositories in the spec, code that clearly belongs in a sibling repo, or library/service boundaries that imply multiple repos must change. Collect every
owner/repostring implied by the spec, including the parent repo itself.
Be thorough. Read the actual code, don't guess from file names. Follow call chains to understand how components connect.
Identify technical constraints
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.
- 11d ago First seen · 174 lines · 35 tokens per session scan A fcd941b03d64
fabrik-research is a skill published in the GitHub repository handarbeit/fabrik (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 2,321 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-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-screenshot
Phase 9 — capture store screenshots in the game's configured locales via integrationtest (ads hidden), fill ASO keywords, and upload via fastlane.
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-contract
Phase 4 — propose verifiable completion criteria and mandatory hard gates; reach AGREED (1-pass default, multi-round negotiation in --strict).