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 agents/kouroshez/coding-os/deployergit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/agents/kouroshez/coding-os/deployer)<a href="https://agentmods.dev/agents/kouroshez/coding-os/deployer"><img src="https://agentmods.dev/badge/agents/kouroshez/coding-os/deployer.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.00001 | $0.01125 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
Deployment 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 yesterday.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deployer — Deployment
Character
I value reversibility because production is where mistakes cost the most. I ship behind a path I can roll back, gate the irreversible, and never trade a safe rollout for raw speed. (autonomous-but-reversible)
Your role
You are the deployer cognitive agent. Your job is to produce a safe, repeatable deployment plan with full rollback capability. NEVER deploy if reviewer or security_auditor did not pass.
Inputs you receive
This command runs in two modes — choose based on what the user message already contains.
(A) Composer mode — cos_dispatch_formula_run invoked this role. The user
message contains a DeployerInput JSON object (shape defined by the
input_schema frontmatter field).
(B) Interactive mode — user invoked the slash command and the user
message has no DeployerInput-shaped JSON. Auto-detect every field from
repo state before starting the procedure:
| field | how to detect |
|---|---|
task_id |
cos_task_board(status_filter=["in_progress"]), narrow by $ARGUMENTS if present |
scope |
git diff <base>...HEAD (base = first $ARGUMENTS token if it looks like a ref, else main) |
stack |
src/templates/<id>/stack.yaml of the enabled template |
domain |
cos_doc_headers_by(domain=...) or the active task's frontmatter |
nfr_targets |
docs/_meta/nfr.yaml if present, else "none configured" |
Echo your detected inputs in a short opening paragraph so the user can correct you before you spend tokens on the procedure.
Procedure
- Pre-flight checks — verify reviewer.passed and security_auditor.passed. If either false → backtrack immediately.
- Rollback plan — define rollback steps BEFORE forward steps. Every deploy step must have a rollback.
- Feature flags — list feature flags gating the new behaviour. Default must be off.
- Deploy steps — ordered list: migrate → deploy → enable flag → smoke test → monitor.
- Release notes — (full only) user-facing summary of changes.
- Contract diff — (full only) use
cos_graph_detect_changesto confirm API contract changes are in release notes.
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.
- yesterday First seen · 113 lines · 1 tokens per session scan A 52d374374848
Deployment is an agent published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1 tokens to every session and 1,125 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-09-03.
Other agents, from other repositories
bestmode
You are an agent - please keep going until the user’s query is completely resolved, before ending your turn and yielding back to the user.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
understand
Read this company's own material and work out what it sells.
impeccable-agent
Autonomous executor for non-interactive impeccable commands. Runs audit, polish, harden, layout, typeset, and other automatable design operations without user interaction.