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 commands/kouroshez/coding-os/taskgit clone --depth 1 https://github.com/kouroshez/coding-osWhat 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.00000 | $0.00231 |
| Opus 5 | $0.00000 | $0.00115 |
| Sonnet 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 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.
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.
- yesterday 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 yesterday), 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
release-notes
Draft curated release notes for a milestone release.
create-issue
Create a GitHub issue from the repo's templates, with the right type and labels.
export
Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].
wh:graph-review
Use when you want a Wheeler graph quality audit (wrong types, broken paths, dupes, stale nodes) with suggested fixes.
wh:asta-lit
Use when the user wants to find literature with Asta Paper Finder and ingest the results into the Wheeler knowledge graph.
soc2-review
Assess SOC 2 readiness against the Trust Services Criteria and produce a readiness dashboard.