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/board)<a href="https://agentmods.dev/commands/kouroshez/coding-os/board"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/board/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/board"><img src="https://agentmods.dev/badge/commands/kouroshez/coding-os/board.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.00311 |
| Opus 5.5 | $0.00000 | $0.00124 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
board 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
Show the current Scrumban board state, grouped by swimlane × status.
Steps:
- Call
cos_task_board(no args → entire board; with$ARGUMENTSinterpreted as swimlane → filter). - Group cards by
swimlanethen bystatus(icebox | in_progress | testing | blocked | complete). - Render the table below. Cap displayed cards per cell at 5 — link to
cos_task_searchfor more. - Surface WIP cap violations at the top (red flag).
- Surface tasks that have been in
in_progress> 3 days at the bottom (stale alert per task-driver escalation ladder).
Template:
## Board — YYYY-MM-DD
### WIP status
| Lane | in_progress | testing | violations |
|---|---|---|---|
### {swimlane}
| icebox | in_progress | testing | blocked |
|---|---|---|---|
| [TASK-NNN] title | ... | ... | ... |
### Stale (in_progress > 3 days)
- [TASK-NNN] {title} — in_progress since {date} ({N} days)
For interactive browsing the human can run cos board --web (opens Hub UI at http://127.0.0.1:9188). Mention this as the visual alternative if the user is exploring a complex state.
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 · 28 lines · 0 tokens per session scan A 1bc5c730063c
board is a command published in the GitHub repository kouroshez/coding-os (7 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 311 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.