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 Koroqe/OPOS --skill deploygit clone --depth 1 https://github.com/Koroqe/OPOSWrote 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/koroqe/opos/deploy)<a href="https://agentmods.dev/skills/koroqe/opos/deploy"><img src="https://agentmods.dev/badge/skills/koroqe/opos/deploy/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/koroqe/opos/deploy"><img src="https://agentmods.dev/badge/skills/koroqe/opos/deploy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.00516 |
| Opus 5.5 | $0.00003 | $0.00206 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 43 lines · 8 tokens per session scan A f19209423091
deploy is a skill published in the GitHub repository Koroqe/OPOS (4 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 516 once invoked, about $0.0000 per session on Opus 5.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
forge-cost
Audit cloud infrastructure costs and produce a concrete optimization plan with specific changes and estimated savings. Use when asked to "how much is this costing", "reduce cloud spend", "cost optimization", "are we overpaying", "cloud bill", or "budget for this infra".
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
forge-infra
Build production-grade infrastructure as code for a service or project. Use when asked to "set up infra", "provision infrastructure", "create cloud resources", "IaC for this project", "terraform for this", or "deploy this service".
touch-release
Set up mobile release pipeline — Fastlane, code signing, CI, beta distribution, versioning. Use when asked about "app store setup", "release pipeline", "fastlane", "beta distribution", or "signing".
forge-diagnose
Diagnose runtime infrastructure issues — cold starts, timeouts, scaling problems, network failures. Use when asked about "infra is slow", "cold starts", "network issues", "why is this timing out", "scaling problem", "latency spikes", or "service is down".
forge-recon
Infrastructure reconnaissance — inventory all cloud resources, map connections, flag risks. Use when asked to "inventory our infra", "what infrastructure do we have", "map our cloud resources", "infra discovery", or "what's running in our cloud".