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 skills/codingagentsystem/cas/cas-supervisor-checklistnpx skills add codingagentsystem/cas --skill cas-supervisor-checklistgit clone --depth 1 https://github.com/codingagentsystem/casWhat 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.00035 | $0.00329 |
| Opus 5 | $0.00017 | $0.00164 |
| Sonnet 5 | $0.00007 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
cas-supervisor-checklist 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 2d 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
Supervisor Checklist
Session Start
- Identify yourself:
mcp__cas__coordination action=whoami - Load EPIC/task context:
mcp__cas__task action=list task_type=epic mcp__cas__task action=ready mcp__cas__task action=list status=blocked - Pull relevant memories and rules:
mcp__cas__search action=search query="<keywords>" doc_type=entry limit=5 - Check worker availability:
mcp__cas__coordination action=worker_status
During Coordination
Record decisions as you go:
mcp__cas__memory action=remember title="..." content="..." tags="decision"
Epic Planning Checklist
- Every subtask has a
demo_statement(if not, it may be a horizontal slice — restructure) - Investigation tasks use
task_type=spikewith question-based acceptance criteria - When multiple approaches exist, a spike with a fit check comparison in
design_notesprecedes implementation tasks
Before Closing an EPIC
- Verify all worker branches are merged into the epic branch
- Confirm task deliverables exist on the epic branch
- Run full test suite on epic branch
Session End
Store a short summary memory tagged summary.
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.
- 2d ago First seen · 46 lines · 35 tokens per session scan A 52165d8e54d6
cas-supervisor-checklist is a skill published in the GitHub repository codingagentsystem/cas (151 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 329 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
gha-security-review
Attack patterns and real-world examples sourced from the HackerBot Claw campaign analysis by StepSecurity (2025): https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation -->.
k8s-security-policies
Comprehensive guide for implementing NetworkPolicy, PodSecurityPolicy, RBAC, and Pod Security Standards in Kubernetes.
monitoring-expert
Observability and performance specialist implementing comprehensive monitoring, alerting, tracing, and performance testing systems.
notion
Use the Notion API to create/read/update pages, data sources (databases), and blocks.
multi-search-engine
Use this skill when ordinary websearch is not enough and you need engine-specific public-web search strategy.
writing-plans
Use when the user asks for an implementation plan or when a coding task is large enough that it should be decomposed before editing.