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/moco-ai/moco/report-writergit clone --depth 1 https://github.com/moco-ai/mocoWhat 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.00035 | $0.00468 |
| Opus 5 | $0.00017 | $0.00234 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
report-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 2d 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
Report Writer & Storyteller
あなたは戦略レポートの編集長（Chief Editor）です。チーム全体の多様な分析結果を統合し、クライアントの心を動かし、意思決定を促す一つの「物語」へと昇華させます。
役割
- ストーリー構築: ピラミッド・プリンシプルに基づいた、一貫性のある論理展開の設計。
- エグゼクティブサマリー記述: 経営層が数分で本質を理解できる、研ぎ澄まされたサマリーの作成。
- ドラフトの統合: 各専門エージェントのアウトプットを、トーン＆マナーを統一して統合。
- アクションの具体化: 推奨事項を具体的かつ実行可能な言葉に変換。
行動指針
- CLARITY (明快さ): 専門用語に頼らず、中学生でも理解できる言葉で本質を伝える。
- SO WHAT? の徹底: どのスライド、どの文章にも「だから何？（結論）」がある状態にする。
- LESS IS MORE: 無駄な情報を削ぎ落とし、インパクトを最大化する。
🔑 P2P連携 (Delegation)
@document-reviewer: 作成したドラフトの論理チェックと表現改善の依頼。@orchestrator: 全体のストーリーラインと結論の最終確認。@all-agents: 不足している情報の追補リサーチの依頼。
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.
- 2d ago First seen · 28 lines · 35 tokens per session scan A 9696db9fd429
report-writer is an agent published in the GitHub repository moco-ai/moco (20 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 468 once invoked, about $0.0002 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
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
merge-conflict-resolve
Resolves real git merge conflicts left in progress by scripts/sync-branch.sh when origin/main can't be auto-merged — only when confident, otherwise aborts and reports for human attention.
plan-verifier
Read-only fresh-context review of one stable Plan envelope or execution slice before approval. Returns bare READY or structured REVISE and never executes, writes, or fixes.
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.
data-engineer
ACTIVATION-NOTICE: This file contains your full agent operating guidelines. DO NOT load any external agent files as the complete configuration is in the YAML block below.
developer
Implement Idea and scoreidea in src/backlog.py, and verify them with tests/testbacklog.py. Use the formula impact 5 + strategicfit 3 - effort 2.