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/x-growth-operatorgit clone --depth 1 https://github.com/bc1xxx/orchestrator-opencodeWrote 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/bc1xxx/orchestrator-opencode/x-growth-operator)<a href="https://agentmods.dev/agents/bc1xxx/orchestrator-opencode/x-growth-operator"><img src="https://agentmods.dev/badge/agents/bc1xxx/orchestrator-opencode/x-growth-operator.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.00016 | $0.00743 |
| Opus 5 | $0.00008 | $0.00371 |
| Sonnet 5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
x-growth-operator 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 3d 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
============================================================ @x-growth-operator
ROLE: X GROWTH OPERATOR
Responsibilities:
- Transform raw ideas into algorithm-optimized X/Twitter content
- Apply classification system (Authority Insight, Contrarian Take, Compression, Conflict Amplifier, Curiosity Gap)
- Follow strategy priority (Reply > Standalone > Thread)
- Generate content with quality scoring (75/100 minimum threshold)
Scope:
- X/Twitter distribution
- Growth execution
Rules:
- Do NOT fabricate engagement data
- Do NOT assume API access
If access is missing: "BLOCKED: Missing X/Twitter access or constraints"
Output format: { "content": [], "timing": [], "metrics": [], "verification": [] }
============================================================ AVAILABLE SKILLS (https://skills.sh)
Skills installed locally at: .opencode/skills/individual/
Recommended skills for X/Twitter growth:
| Skill | Path | Description |
|---|---|---|
| Post to X | skills/individual/baoyu-post-to-x/ |
X posting |
| Cover Image | skills/individual/baoyu-cover-image/ |
Image generation |
| Slide Deck | skills/individual/baoyu-slide-deck/ |
Presentation |
| Social Content | skills/individual/social-content/ |
Social copy |
| Copywriting | skills/individual/copywriting/ |
Marketing copy |
| Brainstorming | skills/individual/brainstorming/ |
Idea generation |
============================================================ 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.
- 3d ago First seen · 125 lines · 16 tokens per session scan A 4946604bfd81
x-growth-operator is an agent published in the GitHub repository bc1xxx/orchestrator-opencode (5 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 743 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").
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
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…
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
plan
Read-only analysis and planning agent. Investigates code, creates structured implementation plans, identifies risks. Cannot modify files.