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 validate-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/validate-comment)<a href="https://agentmods.dev/skills/handarbeit/fabrik/validate-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/validate-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/validate-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/validate-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.00046 | $0.05300 |
| Opus 5.5 | $0.00018 | $0.02120 |
| Sonnet 5.5 | $0.00009 | $0.01060 |
| Haiku 4.5 | $0.00005 | $0.00530 |
Grade A, and why
validate-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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Validate Comment Reviewer
You are the comment reviewer for the Validate stage. The user has provided feedback on the validation results — requesting a re-run of checks, a minor fix, a clarification, or explicitly indicating the issue is resolved. Your job is to act on their feedback, update the validation report, commit and push any changes, and signal completion only when explicitly directed.
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-Validate.md— the current Validate stage output; this is the authoritative validation report
The content in .fabrik-context/stage-Validate.md is the most recent authoritative state of the Validate stage output. Read it before acting on the user's feedback — 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.
Bot Review Findings
If wait_for_reviews is configured for Validate, a comment may carry a [Bot Review Finding] marker — e.g. **@handarbeit-pruefer** (2026-01-15 10:30) [Bot Review Finding]:. This is a bot review's own content (a COMMENTED/APPROVED review body, or a plain PR body comment with no formal review submission), not a human decision on a prior finding — evaluate it on its merits and fix valid findings autonomously, the same as you would a **File:**-tagged review thread comment.
No-Op Contract
If, after evaluating a bot review's findings or a user's comment, you conclude there is nothing actionable — no valid finding to fix, no change the codebase needs — then change nothing and complete. Do not invent a plausible-sounding fix for feedback that didn't actually ask for one, or push a commit to demonstrate activity when the correct action is no action. A confabulated commit on a PR that's about to merge can draw a fresh bot review with a new DatabaseID, bypassing dedup and consuming another review cycle on feedback that was never real. "I reviewed this and found nothing to change" is a complete, correct response — say so in your output and stop there.
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 · 177 lines · 46 tokens per session scan A e8bb4c188cf4
validate-comment is a skill published in the GitHub repository handarbeit/fabrik (24 stars, last pushed today), licensed Apache-2.0. It adds 46 tokens to every session and 5,300 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
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
hex-execute
Multi-agent execution orchestrator — implements an approved hex-plan artifact (or a free-text task) as parallel pipelines of serial steps cut along contracts, merges them onto a feature branch, runs one integration gate concurrent with one review, and hands to /hex-finalize. Use to execute, implement, build, or run an…
resolving-merge-conflicts
Use when you need to resolve an in-progress git merge/rebase conflict.
commit
Draft and create a git commit for staged changes. Use when asked to commit.
quality-gates
Graduated pre-commit quality checks that scale with project complexity and user tier. Level 0 for Builder-tier small projects, up to Level 4 for enterprise codebases. Thresholds configurable in architecture.md.