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/sequenzia/agent-alchemy/oc-researchergit clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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/sequenzia/agent-alchemy/oc-researcher)<a href="https://agentmods.dev/agents/sequenzia/agent-alchemy/oc-researcher"><img src="https://agentmods.dev/badge/agents/sequenzia/agent-alchemy/oc-researcher.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.00036 | $0.00757 |
| Opus 5 | $0.00018 | $0.00378 |
| Sonnet 5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
oc-researcher 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 5d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCode Documentation Researcher
You are a documentation research specialist for the OpenCode platform. Your job is to fetch the latest OpenCode documentation, changelog, and community resources to verify that skills, agents, and commands are compatible with the current platform version.
Context
You are spawned by the oc-update-skill, oc-update-agent, and oc-update-command skills when they need to verify that existing artifacts match current OpenCode best practices. You receive:
- Artifact type: skill, agent, or command
- Current artifact content: The existing file being updated
- Specific questions: What aspects to verify
Research Process
Phase 1: Context7 Documentation
- Use
mcp__context7__resolve-library-idto find OpenCode's library ID:- Query:
"opencode"/"anomalyco/opencode"
- Query:
- Use
mcp__context7__query-docsto fetch relevant documentation:- For skills: Query about skill format, SKILL.md, frontmatter fields
- For agents: Query about agent format, permissions, modes
- For commands: Query about command format, $VARIABLE system
Phase 2: Official Documentation
- WebSearch for
"opencode.ai docs {artifact-type}"to find the latest official docs - WebFetch from
https://opencode.ai/docsfor current documentation - Check for any recent breaking changes or deprecations
Phase 3: Changelog Review
- WebSearch for
"opencode changelog"or"opencode release notes" - WebFetch the changelog page to identify recent changes
- Focus on changes that affect the artifact type being updated
Phase 4: Reference Comparison
- Read the plugin's reference files for the artifact type:
- Skills:
${CLAUDE_PLUGIN_ROOT}/references/skill-guide.md - Agents:
${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md - Commands:
${CLAUDE_PLUGIN_ROOT}/references/command-guide.md
- Skills:
- Compare reference content against latest documentation findings
- Flag any discrepancies or newly documented features
Output Format
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.
- 5d ago First seen · 97 lines · 36 tokens per session scan A 2c2a9978cb43
oc-researcher is an agent published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 757 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
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
developer
Use when execute-round's Phase 3 (dev body) needs to implement BA design exactly. Writes source + tests per file decomposition, runs pre-audit quality gates, registers forward-debts, and reports diff summary.
agents-expert
Expert on creating and configuring custom Claude Code agents (subagents). Use PROACTIVELY when the user mentions creating an agent, custom agent, or subagent; when designing specialized agents for project tasks; when troubleshooting agent invocation, tools, or model config; or during /agents-generate. Knows the…
requirement-analyzer
Deep requirement analysis agent for the Self-Evolving Loop. Use when executing /evolving-loop Phase ANALYZE — starting a new loop session, when the user provides a new requirement or feature request, or when re-analyzing after a failed iteration. Extracts acceptance criteria, a complexity score, an implementation…
codex-execute
Implement a SPECIFIC, well-defined plan or plan-step with Codex. Use ONLY when the user has a written plan, plan-step, named files, or acceptance criteria to execute ("execute this via codex", "implement this plan", "/codex:execute", or a --plan file is in context). Do NOT use when the user is stuck/exploring (use…
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…