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 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/implement-comment)<a href="https://agentmods.dev/skills/handarbeit/fabrik/implement-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/implement-comment/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/implement-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/implement-comment.svg" alt="Reviewed on agentmods" width="80" 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.04069 |
| Opus 5.5 | $0.00015 | $0.01628 |
| Sonnet 5.5 | $0.00008 | $0.00814 |
| Haiku 4.5 | $0.00004 | $0.00407 |
Grade A, and why
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 3d 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 — 163 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 the tests pass for the changed area (see "Which tests to run locally" below for which tests to run)
- 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
Which tests to run locally — .fabrik-context/ci-status.md
When the item has a linked PR, the engine writes .fabrik-context/ci-status.md before this invocation: the PR number, head_sha (the PR head), verdict (green, red, pending, none or unknown), ci_gated (true when this stage waits for CI via wait_for_ci), ci_gate_ahead (true when a later stage waits for CI), written_at and, when the verdict is red, a ## Failing checks section naming each failing check with its conclusion, details URL and whatever output the check produced (title, summary, annotations — often the names of the failing tests). A CI gate stands behind your push when ci_gated or ci_gate_ahead is true; the per-path list below says what that means for each way you can be invoked. Read the file first and find the row below that matches; it decides what you run locally. Check the rows top to bottom and use the first that matches.
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.
- 3d ago First seen · 163 lines · 38 tokens per session scan A a1b3fef921f3
implement-comment is a skill published in the GitHub repository handarbeit/fabrik (24 stars, last pushed today), licensed Apache-2.0. It adds 38 tokens to every session and 4,069 once invoked, about $0.0002 per session on Opus 5.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-10-13.
Other skills, from other repositories
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
lerna
Best practices for Lerna monorepo management, versioning, and publishing.
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
apex-status
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
github-activity
Report what happened across GitHub repositories over a time window, read only. Invoke when the user asks what merged, which issues were opened or closed, or what moved between milestones since a date or since the last report, across one or more repositories.