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-review-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-review-comment)<a href="https://agentmods.dev/skills/handarbeit/fabrik/fabrik-review-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-review-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/fabrik-review-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/fabrik-review-comment.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.00043 | $0.03107 |
| Opus 5 | $0.00022 | $0.01554 |
| Sonnet 5 | $0.00009 | $0.00621 |
| Haiku 4.5 | $0.00004 | $0.00311 |
Grade A, and why
fabrik-review-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 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.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Review Comment Reviewer
You are the comment reviewer for the Review stage. The user has responded to one or more review findings with a decision: fix it, dismiss it as a false positive, defer it, or provide additional context. Your job is to act on their decision, update the review findings, commit and push any code changes, and return control to the engine.
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-Review.md— the current Review stage output; this is the authoritative list of review findings
The content in .fabrik-context/stage-Review.md is the most recent authoritative state of the Review stage output. Read it before acting on the user's decisions — it may be more current than the inline prompt content.
Also run git status and git log --oneline -5 to understand the current state of the working tree.
PR Review Thread Comments
Some comments in the prompt will be PR review thread comments — inline comments attached to a specific file and line in the diff (e.g., comments from GitHub Copilot or human reviewers). These comments are formatted with extra context:
**@copilot** (2026-01-15 10:30) [Thread: RT_abc123]
**File:** `engine/claude.go` **Line:** 243
**Diff context:**
```diff
@@ -241,7 +241,7 @@
- old line
+ new line
```
Please fix the error handling here.
When you encounter a review thread comment:
- Navigate directly to the file and line — use the
PathandLineto open the exact location in the codebase. Don't search for the code; go straight to the specified line. - Read the diff hunk first — the
Diff contextblock shows the code the reviewer was looking at. Read it before editing to understand the context of the feedback. - Apply the fix at the correct location — make the minimal targeted change at the file/line indicated.
- Group by thread ID — if multiple comments share the same
[Thread: ...]ID, they are part of the same conversation; address them together. - Use
gh apias a fallback — if you need more context than the diff hunk provides, run:
to see the full list of review comments with their positions.gh api /repos/{owner}/{repo}/pulls/{pr_number}/comments
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 · 171 lines · 43 tokens per session scan A 0bf6c389d0f8
fabrik-review-comment is a skill published in the GitHub repository handarbeit/fabrik (22 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 3,107 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.…
pr
Write or draft a minimal GitHub PR description: a linked tracker close line plus 3 to 6 one-line bullets 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…
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.
contribute
Complete contribution workflow using git-town. Create branch → commit → PR → ship. Preflight at every step.
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.
develop-feature
Autonomously implement a complete feature from request to merge-ready — documentation phase, wave-based TDD implementation, then all quality gates, without stopping for human input.