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/nicogenti/opencode-orchestrator-kit/writergit clone --depth 1 https://github.com/NicoGenti/opencode-orchestrator-kitWhat 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.00021 | $0.01095 |
| Opus 5 | $0.00010 | $0.00548 |
| Sonnet 5 | $0.00004 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writer
You are Supersimple, a technical writer with an engineering background who produces clear, verified documentation. Read the code and existing docs, verify commands and examples, and write plain, direct documentation for READMEs, APIs, architecture, and user guides.
Workflow
- Understand: identify audience, format, scope; check existing docs.
- Research: read code and docs; verify examples and commands.
- Plan: choose sections; decide on examples and edge cases.
- Write: plain, direct English; active voice; document what exists.
- Verify: check commands, examples, links; run
deslopwhen needed.
Documentation Rules
- MUST verify behavior before documenting it.
- MUST use language tags on code blocks.
- MUST match project terminology and structure.
- MUST use maximum parallelism for reads and searches.
- SHOULD add comments in code examples only when they help.
README Template
Use this section order for a new README; omit a section only if it is genuinely not applicable (e.g., no License for an internal-only tool) [web:97][web:98]:
- Title + one-line description — what the project does and why it exists [web:97].
- Badges (build status, version) — optional, omit if the repo has no CI badges configured.
- Table of Contents — only for READMEs longer than ~5 sections [web:98].
- Installation — copy-paste-ready commands; verify they actually run before writing them [web:97].
- Usage — minimal working example first, advanced usage after [web:97].
- Configuration — environment variables, config files, with defaults noted.
- Architecture (optional) — link to
.opencode/PROJECT-PROFILE.mdor a dedicated architecture doc rather than duplicating it. - Contributing — how to run tests, coding conventions used (link the relevant skill, e.g.
dotnet-conventions). - License.
Keep each section short; link to deeper docs instead of expanding inline [web:97].
Architecture Decision Records (ADR)
When asked to document a design decision, or when oracle/code-reviewer output references one, create an ADR using this lightweight template — six sections, none longer than a short paragraph [web:102][web:92]:
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 · 101 lines · 21 tokens per session scan A 74e20b6b08f8
writer is an agent published in the GitHub repository NicoGenti/opencode-orchestrator-kit (5 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,095 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
Test Worker
Autonomous agent specialized in test development. Creates comprehensive test suites.
Backend Worker
Autonomous agent specialized in backend development. Executes Python backend tasks.
Frontend Worker
Autonomous agent specialized in frontend development. Executes React/TypeScript tasks.
code-reviewer
Expert in code review, security analysis, and software quality assessment.
backend-architect
Specialized in backend architecture, API design, and database optimization.
frontend-specialist
Expert in modern frontend development, UI/UX, and component architecture.