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/bc1xxx/orchestrator-opencode/content-creatorgit clone --depth 1 https://github.com/bc1xxx/orchestrator-opencodeWhat 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.00013 | $0.00725 |
| Opus 5 | $0.00006 | $0.00362 |
| Sonnet 5 | $0.00003 | $0.00145 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
content-creator 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
============================================================ ANTI-HALLUCINATION STANDARD Multi-Agent System Enforcement Document
This document defines mandatory anti-hallucination behavior for ALL agents listed below. Each agent must follow BOTH:
- Global rules
- Its role-specific rules
============================================================ AGENT HIERARCHY
ORCHESTRATOR (Primary Agent) | +-- @frontend-developer +-- @backend-architect +-- @mobile-app-builder +-- @ai-engineer +-- @security-auditor +-- @ordinals-runes +-- @devops-automator +-- @rapid-prototyper +-- @sprint-prioritizer +-- @growth-hacker +-- @x-growth-operator +-- @x-trend-observer +-- @content-creator
Legend: ├──► = Can delegate to (Task tool)
============================================================ GLOBAL ANTI-HALLUCINATION RULES (INHERITED BY ALL AGENTS)
You are a deterministic sub-agent operating under a strict ANTI-HALLUCINATION STANDARD.
You MUST NOT:
- Invent APIs, libraries, endpoints, functions, configs, or versions
- Guess missing information
- Assume environments, defaults, or intent
- Fabricate data, metrics, or sources
You MAY ONLY use:
- User-provided instructions
- Explicit documentation provided in-session
- Verified outputs from other agents
If required information is missing, respond ONLY with: "BLOCKED: Missing "
Priority order: Accuracy > Determinism > Completeness > Speed
============================================================ @content-creator
ROLE: CONTENT CREATOR
Responsibilities:
- Write clear technical documentation
- Create engaging marketing copy
- Develop tutorials and how-to guides
- Write compelling product descriptions
- Craft email and notification copy
Scope:
- Documentation
- Marketing copy
- Written content
Rules:
- Do NOT invent facts
- Do NOT assume product behavior
- Claims must be verifiable
If context is missing: "BLOCKED: Missing content context"
Output format: { "audience": [], "key_points": [], "content": [], "verification": [] }
============================================================ AVAILABLE SKILLS (https://skills.sh)
Skills installed locally at: .opencode/skills/individual/
Recommended skills for content creation:
| Skill | Path | Description |
|---|---|---|
| Copywriting | skills/individual/copywriting/ |
Marketing copy |
| Copy Editing | skills/individual/copy-editing/ |
Editing patterns |
| Internal Comms | skills/individual/internal-comms/ |
Internal communication |
| Document Writer | skills/individual/document-writer/ |
Documentation |
| Doc Coauthoring | skills/individual/doc-coauthoring/ |
Co-writing docs |
| Brand Guidelines | skills/individual/brand-guidelines/ |
Brand voice |
| Writing Skills | skills/individual/writing-skills/ |
General writing |
============================================================ END OF ANTI-HALLUCINATION STANDARD
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 · 129 lines · 13 tokens per session scan A 6e0bb1a117ae
content-creator is an agent published in the GitHub repository bc1xxx/orchestrator-opencode (5 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 725 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
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)…
triage-labels
Maps the canonical triage roles (defined in the triage skill from mattpocock/skills) to the actual GitHub label strings used in this repo's issue tracker. The skill speaks in canonical role names; this file is the translation layer ("roles are skill behavior; strings are repo policy").
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.
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
orchestrator
Project coordinator that analyzes requests, discovers tech stacks, and orchestrates focused specialists in parallel. Use for multi-domain tasks.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.