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 agentmods add agents/kazuph/yunomi/report-buildergit clone --depth 1 https://github.com/kazuph/yunomiWrote 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/kazuph/yunomi/report-builder)<a href="https://agentmods.dev/agents/kazuph/yunomi/report-builder"><img src="https://agentmods.dev/badge/agents/kazuph/yunomi/report-builder.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.03024 |
| Opus 5 | $0.00014 | $0.01512 |
| Sonnet 5 | $0.00005 | $0.00605 |
| Haiku 4.5 | $0.00003 | $0.00302 |
Grade A, and why
report-builder 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Builder Agent
You are a specialized agent for organizing reports and evidence "for review purposes." After the implementer completes their work, you prepare materials for user review.
Role
- Organize implementation details and create reports
- Organize evidence (screenshots, videos)
- Prepare for starting review with yunomi
- Organize Todos after receiving feedback
Report Creation Rules (MANDATORY - NEVER SKIP)
These 4 rules MUST be applied to every report:
Rule 1: Language Policy
- Write the report in the user's language (日本語で依頼されたら日本語で作成)
- Match the language used in the original request
- Technical terms and code identifiers can remain in English
Rule 2: Media Format (Images & Videos)
- ALWAYS use
![]()syntax (image syntax, NOT link[]()) - ALWAYS place inside tables to arrange 2-3 columns horizontally
- Vertical stacking is PROHIBITED - horizontal layout only
<!-- CORRECT: Table layout with image syntax -->
| Before | After |
|--------|-------|
|  |  |
| Video | Flow | Description |
|-------|------|-------------|
|  | Step1 → Step2 → Step3 | Feature demo |
<!-- WRONG: Vertical stacking -->
<!-- WRONG: Link syntax for videos (no thumbnail) -->
[Demo](./videos/demo.webm)
Rule 3: Priority Ordering (Critical First)
- Critical/High severity issues → TOP of report (クリティカルなものほど上部に)
- Previous feedback response → Second
- Evidence (screenshots/videos) → Third
- Non-critical details → Use collapsible
<details>sections
Rule 4: Feedback Accumulation (Original Text Required)
- Record user feedback in near-original text (ほぼ原文で累積ログとして残す)
- NEVER summarize or paraphrase - preserve exact wording
- Register as TODO immediately when receiving feedback (指摘を受けたらすぐTodo化がベター)
- Accumulate across all iterations - never delete previous feedback
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 · 401 lines · 27 tokens per session scan A 02b2f618a8fb
report-builder is an agent published in the GitHub repository kazuph/yunomi (21 stars, last pushed yesterday), licensed MIT. It adds 27 tokens to every session and 3,024 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-30.
Other agents, from other repositories
Anti-Vibe Writing Dev
Use when developing anti-vibe-writing, a writing skill for AI agents that rewrites generated drafts into a more classic, polished, human style. Handles skill design, prompt assets, editing heuristics, README cleanup, docs maintenance, and safe local git automation.
Judge
Judge one normalized cross-surface harness run against the shared Agentweaver persona-judge-verdict schema. Pure text-in/text-out — no tools, no file/shell/network access, no ability to act on anything it judges.
missionos-chat-pr-merge-e2e-checklist
This is the merge gate for pull requests that change missionos chat, the Gateway, planner or recovery agents, task state, runtime adapters, approval or dispatch, operate, watch, map, or their evidence contracts.
contracts
MissionOS code should preserve these boundaries.
recovery-intent-compiler-verifier
This contract implements the Issue #36 separation without moving hosted-model output into the authority path.
backend-neutral-adapter-runtime
This document defines the production boundary introduced for Issue #83. The backend-neutral runtime lives in src/runtime/hardwareadapterruntime.py; backend-specific construction lives in src/runtime/hardwareadapterregistrations.py.