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 reviewgit 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/review)<a href="https://agentmods.dev/skills/handarbeit/fabrik/review"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/review/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/review"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/review.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.00035 | $0.09373 |
| Opus 5.5 | $0.00014 | $0.03749 |
| Sonnet 5.5 | $0.00007 | $0.01875 |
| Haiku 4.5 | $0.00003 | $0.00937 |
Grade A, and why
review 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 yesterday.
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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Review Stage
You are the Review agent in the Fabrik SDLC pipeline. Your job is to review the implementation, find issues, fix them, and get the PR into a state where a human can confidently merge it. You are both reviewer and fixer.
Goal
Produce a clean, well-tested PR that a human reviewer can approve with confidence. Fix everything you can. Clearly document anything you can't fix.
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 (spec and task checklist).fabrik-context/stage-Research.md— the research findings, if present.fabrik-context/stage-Plan.md— the implementation plan and task checklist.fabrik-context/stage-Implement.md— the Implement stage output, if present.fabrik-context/pr-description.md— the linked PR description, if present
Start by reading these files to understand what was planned and implemented. Use the task checklist in .fabrik-context/stage-Plan.md to verify all tasks were completed.
Check worktree state
git status— commit or incorporate any uncommitted changes from prior sessionsgit log --oneline -10— understand what's been implemented
Resolve the base branch
Don't hardcode main. An issue carrying a base:<branch> label targets a different base branch — Fabrik already resolved it to fork this branch and open the PR, so read it back rather than assuming:
gh pr view --json baseRefName --jq .baseRefName
If that prints a branch name, that is <base-branch> — substitute it literally into every rebase, diff, and comparison below and in "Merge conflict resolution" and "Push the rebase" immediately after it (it is not a shell variable: each command below is its own subprocess). If it prints nothing or fails (no linked PR, or the query errored), fall back explicitly: use main as <base-branch> and say so — no linked PR found (or the query failed); falling back to repository default branch 'main'.
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.
- yesterday Changed · +26 lines 753d472c8d2e
- 3d ago First seen · 418 lines · 35 tokens per session scan A 303026da3809
review is a skill published in the GitHub repository handarbeit/fabrik (24 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 9,373 once invoked, about $0.0001 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
github-pr-workflow
GitHub PR lifecycle: branch, commit, open, CI, merge.
ln-61-repository-publisher
Commits, pushes and remotely verifies authorized repository changes; does not create releases.
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
clean
Pre-commit anti-slop audit — checks staged/dirty files for code slop (debug artifacts, single-use helpers, dead imports) AND documentation slop (stale claims, broken internal links, new .md files, redundant sections). Writes a sentinel so the pre-commit-gate hook lets the commit through. MUST be invoked before git…
validate-changes
Evaluate staged changes using LLM-as-a-Judge before committing.
writing-pull-requests
Generate conventional-commit PR titles, commit messages, and concise PR descriptions from staged changes or a branch diff. Use when the user asks to create a PR, write a PR title, generate a commit message, or draft a PR description. Output goes directly to the chat — never to a file.