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.
git 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/commands/kouroshez/coding-os/task)<a href="https://agentmods.dev/commands/kouroshez/coding-os/task"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/task/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/commands/kouroshez/coding-os/task"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/task.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.00000 | $0.00231 |
| Opus 5.5 | $0.00000 | $0.00092 |
| Sonnet 5.5 | $0.00000 | $0.00046 |
| Haiku 4.5 | $0.00000 | $0.00023 |
Grade A, and why
task 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
Load and summarize the task specified by $ARGUMENTS.
Steps:
- Run
cos task-show $ARGUMENTS(or read the task detail file directly from docs/tasks/) - Read the full task detail file — including Notes and Session Checkpoint sections
- Classify the task domain and identify which playbook applies
- Present a summary:
- Goal: why this task exists (1-2 sentences)
- Domain: which playbook route
- Scope: Small / Medium / Large (based on file count and complexity)
- Requirements: the Given/When/Then acceptance criteria
- Dependencies: any prerequisite tasks and their status
- Verification: what commands to run when done
- Session Checkpoint: any previous progress (if exists)
- Ask: "What would you like to do? (a) Start — run Classify → Orient → Plan → Execute, (b) Investigate first, (c) Mark as blocked"
If no task number is provided, run cos task-pick to suggest the next task.
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 · 18 lines · 0 tokens per session scan A c9e674d80fc3
task is a command published in the GitHub repository kouroshez/coding-os (6 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 231 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-08-31.
Other commands, from other repositories
maestro-ralph
Closed-loop policy over the canonical Session/Run chain.
maestro-session-manage
Manage a v3 Session — inspect status/resume-view, review knowledge candidates, complete, archive/unarchive.
maestro
Intent-to-chain planner over the canonical Session/Run lifecycle.
converge
Bash: python /scripts/aco.py --session {rundir}/work/team report.
maestro-issue
A command for managing issues, which are tracked problems or tasks, through their full lifecycle.
twining:status
Show Twining project coordination status.