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 skills/sequenzia/agent-alchemy/oc-update-agentnpx skills add sequenzia/agent-alchemy --skill oc-update-agentgit 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/skills/sequenzia/agent-alchemy/oc-update-agent)<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/oc-update-agent"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/oc-update-agent.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.00062 | $0.01257 |
| Opus 5 | $0.00031 | $0.00629 |
| Sonnet 5 | $0.00012 | $0.00251 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
oc-update-agent 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 4d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update OpenCode Agent
You are initiating the OpenCode agent update workflow. This process locates an existing agent, researches current platform best practices, analyzes the agent for outdated patterns, and applies updates with validation.
Critical Rules
AskUserQuestion is MANDATORY
IMPORTANT: You MUST use the AskUserQuestion tool for ALL questions to the user. Never ask questions through regular text output.
Phase 1: Load References
Read the OpenCode platform overview and agent guide:
- Read
${CLAUDE_PLUGIN_ROOT}/references/platform-overview.md - Read
${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md
Phase 2: Locate Agent
Find the agent to update.
If $ARGUMENTS is provided:
- Check if the argument is a file path — read it directly
- If it's an agent name — search for
{name}.mdin known directories
If no arguments:
- Search for OpenCode agents in the workspace:
Globfor.opencode/agents/*.mdGlobfor~/.config/opencode/agents/*.md
- Present found agents using
AskUserQuestion:- Header: "Select Agent"
- Question: "Which agent would you like to update?"
- Options: List found agents (up to 4; include "Other" for custom path)
Read the selected agent file and store its contents.
Phase 3: Research
Spawn the researcher agent to check latest documentation:
Task:
subagent_type: "agent-alchemy-opencode-tools:oc-researcher"
prompt: |
Research the latest OpenCode documentation for agent format compatibility.
Artifact type: agent
Current artifact content:
---
{contents of the agent file}
---
Specific questions:
1. Are there any new agent frontmatter fields?
2. Have permission syntax rules changed?
3. Are there new agent modes or capabilities?
4. Any changes to subagent behavior or limitations?
Reference guide: ${CLAUDE_PLUGIN_ROOT}/references/agent-guide.md
Phase 4: Analyze
Compare the existing agent against current best practices:
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.
- 4d ago First seen · 180 lines · 62 tokens per session scan A e6a2dca9d4d8
oc-update-agent is a skill published in the GitHub repository sequenzia/agent-alchemy (43 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,257 once invoked, about $0.0003 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 skills, from other repositories
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese specialist role catalogs.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.