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/re-cinq/wave/opsxnpx skills add re-cinq/wave --skill opsxgit clone --depth 1 https://github.com/re-cinq/waveWhat 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.00026 | $0.00648 |
| Opus 5 | $0.00013 | $0.00324 |
| Sonnet 5 | $0.00005 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
opsx 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSpec Workflow (OpsX)
OpenSpec Workflow (OpsX) provides a comprehensive lifecycle management system for specification-driven development changes, from initial proposal through implementation and archival.
Overview
OpsX implements a structured lifecycle:
- Onboard - Get started with OpenSpec workflow
- New - Create new OpenSpec change proposals
- Fast-Forward - Generate complete planning documentation
- Apply - Execute implementation tasks
- Archive - Complete and archive finished changes
Available Commands
| Command | Purpose | Usage |
|---|---|---|
opsx.onboard |
Get started with OpenSpec workflow | /opsx.onboard |
opsx.new |
Create a new OpenSpec change proposal | /opsx.new "change description" |
opsx.ff |
Fast-forward to generate all planning docs | /opsx.ff |
opsx.apply |
Execute OpenSpec implementation tasks | /opsx.apply |
opsx.archive |
Archive a completed OpenSpec change | /opsx.archive |
Standard Workflow
# Full lifecycle
/opsx.onboard # first time only
/opsx.new "Add user authentication system"
/opsx.ff # generate planning docs
/opsx.apply
/opsx.archive
# Quick implementation (urgent/small fixes)
/opsx.new "Fix critical security vulnerability"
/opsx.apply
/opsx.archive
Change Structure
.openspec/
├── changes/
│ └── [change-id]/
│ ├── proposal.md # Initial change proposal
│ ├── specification.md # Detailed requirements
│ ├── plan.md # Implementation plan
│ ├── tasks.md # Task breakdown
│ ├── implementation/ # Implementation artifacts
│ └── archive.md # Completion summary
└── archive/
└── [year]/[change-id]/ # Archived change artifacts
Lifecycle Phases
| Phase | Command | Key Artifacts |
|---|---|---|
| Proposal | opsx.new |
proposal.md |
| Planning | opsx.ff |
specification.md, plan.md, tasks.md |
| Implementation | opsx.apply |
Code, tests, docs in implementation/ |
| Archive | opsx.archive |
archive.md with completion summary |
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.
- 2d ago First seen · 83 lines · 26 tokens per session scan A c215ceb920b2
opsx is a skill published in the GitHub repository re-cinq/wave (20 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 648 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-30.
Other skills, from other repositories
coordinate-agents
Route Codex-native multi-agent orchestration in a Git repository through a local-first, recoverable Agent Bus. Use for role-based planning, task execution, review, recovery, adapters, and human-gated release workflows. The plugin supports Codex CLI, Google Antigravity CLI, Claude, and other configured coding agents.…
coordinate-task
Run a Coordinate Agents Task from requirement clarification through planning, implementation, review, and the human release gate. Hide Agent Bus transport details behind the durable Task API.
coordinate-recover
Diagnose and safely resume Coordinate Agents Tasks after executable failure, non-zero exit, timeout, stale claim, processing message, or Implementer ERROR. Recovery is explicit and never an automatic retry loop.
coordinate-setup
Discover coding CLIs on the current computer and configure a Coordinate Agents implementation agent. Use for setup, executable checks, registered agents, user-level configuration, and project-over-user precedence.
coordinate-review
Review a Coordinate Agents implementation as the Codex Reviewer. Verify the real commit, diff, tests, validation evidence, and specification without modifying the Implementer's product code.
api-contracts
Enforce API contract governance, strict backward compatibility, schema validation, and standardized RFC 7807 error responses.