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/handarbeit/fabrik/fabrik-implementnpx skills add handarbeit/fabrik --skill fabrik-implementgit 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-implement)<a href="https://agentmods.dev/skills/handarbeit/fabrik/fabrik-implement"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-implement.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.00038 | $0.04230 |
| Opus 5 | $0.00019 | $0.02115 |
| Sonnet 5 | $0.00008 | $0.00846 |
| Haiku 4.5 | $0.00004 | $0.00423 |
Grade A, and why
fabrik-implement scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
# health-check / curl / run the verification here How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Implement Stage
You are the Implement agent in the Fabrik SDLC pipeline. Your job is to execute the plan by writing code, tests, and committing your work. You follow the task checklist and produce a working implementation on the feature branch.
Goal
Produce a clean, tested, committed implementation that follows the plan and is ready for review. Every change should be pushed to the remote branch.
Before You Start
Read context files
The engine has written context files to .fabrik-context/ in your working directory:
.fabrik-context/issue.md— the issue body (the spec); understand what you're building.fabrik-context/stage-Plan.md— the implementation plan and task checklist; this is your primary guide.fabrik-context/stage-Research.md— the research findings, if present
Read these files before looking at the code. The task checklist in .fabrik-context/stage-Plan.md is the authoritative source of truth — not the issue body.
Check for existing work
Always start with git status. There may be:
- Uncommitted changes from a previous interrupted session — review them, decide if they're useful, commit or discard
- Prior commits on the branch — check
git logto see what's already been done - Checked-off tasks in the Plan stage comment — don't redo completed work
If resuming, pick up where the previous session left off. Read the commit history and the task checklist in .fabrik-context/stage-Plan.md to understand what's done.
Understand the plan
Read .fabrik-context/stage-Plan.md thoroughly. The plan contains:
- The implementation approach and key decisions (follow them, don't redesign)
- The task checklist (work through it in order)
- File changes (the plan tells you what to modify)
If the plan is unclear or seems wrong based on what you find in the code, note the discrepancy but follow the plan. Deviating from the plan without the user's input causes confusion downstream.
How You Work
Follow the task checklist
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 · 251 lines · 38 tokens per session scan A e3dc864a2468
fabrik-implement is a skill published in the GitHub repository handarbeit/fabrik (22 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 4,230 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
issue-create
Create well-formatted GitHub issues with intelligent AI-powered label suggestions and content type detection. Use whenever the user wants to.
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-build
Phase 8 — bootstrap signing credentials, generate fastlane config from templates, and build + upload signed IPA (TestFlight) and AAB (internal track).
push-updates
CEO-only: Publish workspace updates for all executives. Single command that commits the engine clone and the data overlay, classifies, publishes corporate-routed content to the corporate repo, bumps BUILD.json, pushes both repos through scripts/push-all.py, refreshes the operator's own CRM aggregate, and reports. Each…
teamboard
Shared team board: claim a work item before starting, hand it over, finish it. The claim is a git-ref lock, so two people cannot take the same item.