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/koroqe/opos/deploynpx skills add Koroqe/OPOS --skill deploygit clone --depth 1 https://github.com/Koroqe/OPOSWhat 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.00008 | $0.00516 |
| Opus 5 | $0.00004 | $0.00258 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
deploy 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.
What it actually says
deploy
When to use
A commit on main is ready for production: tests pass on CI, the change has been reviewed (by eng-reviewer), and the on-call engineer is available to monitor.
Inputs
commit_sha— the commit to deploy.target_env— production environment identifier (e.g.prod-us-east,prod-eu-west).
Steps
- Pre-flight checks — verify CI is green for
commit_sha, the change has an approving review fromeng-reviewer, no incidents are active intarget_env. - Run pipeline — invoke the deploy pipeline (placeholder: adopters wire in their actual CI/CD here; could be a
gh workflow run, akubectl apply, etc.). - Verify health — after rollout completes, hit the service's health endpoint and confirm 200 OK, then run smoke tests against
target_env. - Record history entry — write
departments/engineering/.claude/skills/deploy/history/YYYY-MM-DD-<run-id>.mdwith the schema-conformant frontmatter and a body summarizing what was deployed, any anomalies, and the proposed delta (or "none").
Outputs
- Deployed version visible at
target_env's health endpoint. - A history entry recording the run.
- (On failure) An incident reference and a rollback record.
Failure modes
- Build fail — pipeline step 2 fails before rollout. Recovery: do not proceed to step 3; record
outcome: failurewith the failing job's log link. No production change occurred. - Smoke-test fail — step 3 detects bad behavior after rollout. Recovery: trigger the rollback procedure from
PROCESS.md. Recordoutcome: failureandproposed_deltadescribing what the smoke tests caught. - Rollback path — if the deploy must be reversed, follow the rollback procedure in
./PROCESS.md. The rollback itself is a deploy of the prior version; record it as a separate history entry withactor: eng-lead,proposed_delta: <root cause if known>.
Related
- Process definition:
./PROCESS.md - Run history:
./history/
What ships with it
2 files 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 · 43 lines · 8 tokens per session scan A f19209423091
deploy is a skill published in the GitHub repository Koroqe/OPOS (2 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 516 once invoked, about $0.0000 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 skills, from other repositories
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.