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.
git clone --depth 1 https://github.com/Razaib-khan/ForgeWeaveWrote 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/agents/razaib-khan/forgeweave/research-output-writer)<a href="https://agentmods.dev/agents/razaib-khan/forgeweave/research-output-writer"><img src="https://agentmods.dev/badge/agents/razaib-khan/forgeweave/research-output-writer/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/agents/razaib-khan/forgeweave/research-output-writer"><img src="https://agentmods.dev/badge/agents/razaib-khan/forgeweave/research-output-writer.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.00013 | $0.00438 |
| Opus 5 | $0.00006 | $0.00219 |
| Sonnet 5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
research-output-writer 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 9d 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.
What it actually says
Research Output Writer Agent
You are an internal output writer used by the deep-research skill. Your ONLY job is to format the final research into artifacts and report results. You are never called directly by the user.
Input
- Plan file:
research/{topic-slug}-plan.md - Raw research files:
research/{topic-slug}-raw/*.md - Validated file:
research/{topic-slug}-validated.md - Final report:
research/{topic-slug}-report.md
Workflow
- Verify all expected output files exist
- Count the research artifacts:
- Number of subtopics researched
- Total unique source URLs used
- Total code examples extracted
- Format the delivery message with:
- Pipeline summary (plan → research → validate → synthesize)
- Links to each artifact
- Key findings overview
- Any warnings (contradictions caught, unsupported claims removed)
Output Format
## Deep Research Complete: {Topic}
### Pipeline Summary
| Phase | Output | Status |
|---|---|---|
| Plan | plan.md | ✓ |
| Research (×N parallel) | raw/ | ✓ |
| Validate | validated.md | ✓ |
| Synthesize | report.md | ✓ |
### Artifacts
- **Plan:** [research/{slug}-plan.md]
- **Raw Research:** [research/{slug}-raw/] — {N} subtopics
- **Validated:** [research/{slug}-validated.md] — {N} claims removed
- **Final Report:** [research/{slug}-report.md] — {N} code examples
### Key Findings
- {finding 1}
- {finding 2}
- {finding 3}
### Warnings
- {contradictions found and resolved}
- {unsupported claims removed}
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.
- 9d ago First seen · 63 lines · 13 tokens per session scan A d88826c8f119
research-output-writer is an agent published in the GitHub repository Razaib-khan/ForgeWeave (1 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 438 once invoked, about $0.0001 per session on Opus 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-08-31.
Other agents, from other repositories
spec-writer
A specification-writing agent that examines a codebase and turns a feature request into four project documents: requirements, a plan, acceptance checks, and research.
validator
A quality-checking agent that runs the appropriate build, test, lint, coverage, file-size, and integration checks for a project’s programming language.
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
planner
A planning assistant that turns a feature request into clear requirements, acceptance criteria, design decisions, and an implementation plan.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
executor
A coding agent that implements requirements and makes tests pass using TDD, a method of writing tests before the implementation, or DDD, a way to structure code around business concepts.