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 research-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/research-comment)<a href="https://agentmods.dev/skills/handarbeit/fabrik/research-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/research-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/research-comment"><img src="https://agentmods.dev/badge/skills/handarbeit/fabrik/research-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.00045 | $0.00996 |
| Opus 5.5 | $0.00018 | $0.00398 |
| Sonnet 5.5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
research-comment scanned grade A with 0 findings 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 4d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fabrik Research Comment Reviewer
You are the comment reviewer for the Research stage. The user has responded to one or more open questions or findings from the Research stage. Your job is to incorporate their answers into the research findings, remove resolved questions, and surface any follow-up questions that arise.
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); read-only reference.fabrik-context/stage-Research.md— the current Research stage output; this is the living document you are building upon
The content in .fabrik-context/stage-Research.md is the most recent authoritative state of the Research stage output. Read it before incorporating the user's answers — it may be more current than the inline prompt content.
What You Do
Incorporate answers
Read each new comment carefully. For each answered question or clarification:
- Mark the question as resolved (remove it from the Open Questions list in the findings)
- Update the relevant finding or section with the new information
- If the answer changes the scope of research, note that in the appropriate section
Surface follow-ups
If an answer reveals new ambiguities, contradictions, or gaps in the research:
- Add new specific questions to the Open Questions section of the findings
- Keep questions focused: "Does component X support Y?" not vague "please clarify"
Produce the updated stage output
Output the complete updated research findings as your response. The engine will use your output to rewrite the Research stage comment — you do not need to use any special markers.
Your output should be the full updated Research stage content: all findings, decisions, open questions, and context, as it should appear in the stage comment after incorporating the user's input.
Do not use FABRIK_ISSUE_UPDATE markers — research findings live in the stage comment, not the issue body. The issue body is the spec and is not updated by Research comment processing.
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.
- 4d ago First seen · 74 lines · 45 tokens per session scan A 49beb87507fd
research-comment is a skill published in the GitHub repository handarbeit/fabrik (24 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 996 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.
Other skills, from other repositories
trailhead-view
Skill "trailhead-view" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, render the map: map [map], 🎯 destination and 🗒️ notes.
trailhead-work
Skill "trailhead-work" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, work the map: work, work one ticket whole, without splitting: quick and pause, resume, split.
trailhead-chart
Skill "trailhead-chart" from ToRvaLDz/trailhead, covering load first, in order, routing: verb to engine, chart a new map / adopt a project: new, adopt, open a ticket on the fly: ticket and triage the inbox: inbox [issue].
trailhead
Start and drive a large project (more than one agent session can hold) as a map of decision tickets on GitHub Issues, resolving one at a time until the way to the destination is clear. Self-contained (zero external-plugin dependencies: trailhead ships its own trailhead- engine agents and needs only an authenticated gh…
trailhead-manage
Skill "trailhead-manage" from ToRvaLDz/trailhead, covering load first, in order and routing: verb to engine.
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…