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-implement-commentgit 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-comment)<a href="https://agentmods.dev/skills/handarbeit/fabrik/fabrik-implement-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-implement-comment.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.02018 |
| Opus 5 | $0.00019 | $0.01009 |
| Sonnet 5 | $0.00008 | $0.00404 |
| Haiku 4.5 | $0.00004 | $0.00202 |
Grade A, and why
fabrik-implement-comment 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 7d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Implement Comment Reviewer
You are the comment reviewer for the Implement stage. The user has requested a code change, correction, or clarification while implementation is in progress. Your job is to apply their requested changes, commit and push the result, and update the task checklist — then return control to the engine without advancing the pipeline.
Before You Start
Read the context files the engine has written to .fabrik-context/ in your working directory:
.fabrik-context/issue.md— the current issue body (the spec).fabrik-context/stage-Plan.md— the implementation plan and task checklist; the authoritative guide for what is being built
The content in .fabrik-context/stage-Plan.md is the most recent authoritative state of the Plan stage output. Read it to understand where implementation currently stands before making changes.
Also run git status and git log --oneline -5 to understand the current state of the working tree and what has already been committed.
What You Do
Apply the requested change
Read the user's comment carefully. Understand exactly what they are asking for:
- A correction to code already written
- A new or modified requirement that changes an in-progress task
- A clarification about how something should work
- A request to undo or redo part of the implementation
Make the minimal change that satisfies their request. Do not redesign or refactor beyond what was asked.
Commit and push
After making the change:
- Verify the code compiles and tests pass for the changed area
- Commit with a clear message describing what changed and why (reference the user's request)
- Push to the remote branch
Good commit message: Apply user feedback: use interface X instead of concrete type Y
Verifying with a live server or a long-running command
If the user's requested change needs a running instance of the managed app to verify (e.g. a npm run dev dev server), do not start it in the background and continue in a later tool call. Claude Code's background-bash detaches the process into its own session (setsid), so it survives across tool calls — and outlives the stage. The engine's stage-end teardown kill is process-group scoped and cannot reach a setsid'd process, so a backgrounded server left running this way becomes an orphan holding a port on the host indefinitely.
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.
- 7d ago First seen · 119 lines · 38 tokens per session scan A 297c649c3552
fabrik-implement-comment 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 2,018 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
pr-comments
Triage unresolved review threads on an open PR and close them out. Per thread, either agree (fix scoped to THIS PR's diff, verify, commit and push, reply, resolve) or disagree (justify with a quoted citation from the version-matched official doc, reply, resolve). Every reply is drafted for approval before it posts.…
orchestrate
Apply the review lenses yourself, in the solo main loop, with no subagent dispatch. Pick only the lenses the change actually touches, run each as a checklist against real code and real command output, and gate go/no-go on cited evidence. Use when asked to run, use, or review with "our lenses", or to plan or verify a…
pr
Write or draft a minimal GitHub PR description: a tracker close line plus a compact summary of what changed and why, and nothing else (no headings, no Testing block, no screenshots table). Project tokens (repo, tracker prefix, verify commands) are read from .claude/harness/profile.md. Use when running gh pr create /…
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
ai-slop-cleaner
Post-implementation cleanup that removes AI-generated bloat while preserving functionality. Runs pass-by-pass with test verification after each pass. Activate after kraken/spark complete a feature, or when a codebase needs hygiene work.