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 skills add ex-machina-co/opencode-anthropic-auth --skill sync-main-to-v2git clone --depth 1 https://github.com/ex-machina-co/opencode-anthropic-authWrote 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/ex-machina-co/opencode-anthropic-auth/sync-main-to-v2)<a href="https://agentmods.dev/skills/ex-machina-co/opencode-anthropic-auth/sync-main-to-v2"><img src="https://agentmods.dev/badge/skills/ex-machina-co/opencode-anthropic-auth/sync-main-to-v2/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ex-machina-co/opencode-anthropic-auth/sync-main-to-v2"><img src="https://agentmods.dev/badge/skills/ex-machina-co/opencode-anthropic-auth/sync-main-to-v2.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 32 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00000 | $0.00670 |
| Opus 5.5 | $0.00000 | $0.00268 |
| Sonnet 5.5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
sync-main-to-v2 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 1mo 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Syncing main into v2/main
This skill does not describe the synchronization workflow. The workflow lives in one place: the
companion file references/plan.md, beside this skill. That file is a complete VIPER plan and is the
canonical source of truth. This skill only explains how to materialize it and run it.
Load viper-execution-rules before executing anything.
Prerequisites
The viper-plans facet must be installed in the project. It supplies the execution rules and the
plan tools. If neither the plan tools nor .opencode/plans/ are available, say so and stop — do not
improvise a substitute workflow.
Plan tools
The viper-plans MCP server provides viper-write-plan, viper-read-plan, viper-edit-plan,
viper-list-plans, and viper-delete-plan. A client may expose them under a prefixed name such as
viper-plans_viper-write-plan, so treat any tool whose name ends with one of those canonical names
as that tool. Prefer them whenever they are available; otherwise use the file-tool fallback noted
below.
Procedure
-
Read the canonical plan. Read
references/plan.mdrelative to this skill's own directory, as reported when the skill was loaded. Read it in full. -
Materialize it as the runtime plan. Persist that exact content under the plan name
main-to-v2-sync, usingviper-write-planif available; otherwise write.opencode/plans/main-to-v2-sync/plan.mdwith your file tools, creating the directory if needed.Overwrite any existing plan of that name without asking. The plan store holds a generated copy, not the source. Never edit
references/plan.mdto reflect a runtime decision, and never merge a stale runtime copy back into it. -
Execute it immediately. Count the
### Stepheadings, state the plan name and step count in one line, then follow theviper-execution-rulesprotocol: one TODO per step heading, steps in document order, Propose and Review steps gated on the user, and a stop on any Verify failure.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 55 lines · 0 tokens per session scan A 9db00fe94f16
sync-main-to-v2 is a skill published in the GitHub repository ex-machina-co/opencode-anthropic-auth (559 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 670 tokens. 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-09-03.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.