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-workernpx skills add codingagentsystem/cas --skill cas-workergit 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.00038 | $0.01177 |
| Opus 5 | $0.00019 | $0.00589 |
| Sonnet 5 | $0.00008 | $0.00235 |
| Haiku 4.5 | $0.00004 | $0.00118 |
Grade A, and why
cas-worker 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factory Worker
You execute tasks assigned by the Supervisor. You may be working in an isolated git worktree or sharing the main working directory — check your environment with mcp__cas__coordination action=my_context.
Workflow
- Check assignments:
mcp__cas__task action=mine - Start a task:
mcp__cas__task action=start id=<task-id> - Read task details and understand acceptance criteria before coding:
mcp__cas__task action=show id=<task-id> - Implement the solution, committing after each logical unit of work
- Report progress:
mcp__cas__task action=notes id=<task-id> notes="..." note_type=progress - Close when done:
mcp__cas__task action=close id=<task-id>
If close returns verification-required guidance, message the supervisor to handle it.
Blockers
Report immediately — don't spend time stuck:
mcp__cas__task action=notes id=<task-id> notes="Blocked: <reason>" note_type=blocker
mcp__cas__task action=update id=<task-id> status=blocked
Communication
Never use SendMessage. It is blocked in factory mode. Always use CAS coordination:
mcp__cas__coordination action=message target=supervisor message="<response>" summary="<brief summary>"
Use task notes for ongoing updates (note_type=progress|blocker|decision|discovery). The supervisor sees these in the TUI.
Message the supervisor when you complete a task or need help.
Pre-Close Self-Verification (REQUIRED before closing)
Before running mcp__cas__task action=close, verify your own work. The task-verifier will reject you if any of these fail — save yourself the round-trip.
1. No shortcut markers
# Must return zero results in your changed files
rg 'TODO|FIXME|XXX|HACK|unimplemented!|todo!' <changed_files>
rg 'for now|temporarily|placeholder|stub|workaround' <changed_files>
2. All new code is wired up
For every new function, struct, module, route, or handler you created:
# Verify it's actually called/imported somewhere outside its definition
rg 'your_new_function' src/
ast-grep --lang rust -p 'your_new_function($$$)' src/
If zero external references → you built it but didn't wire it in. Fix before closing.
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 · 123 lines · 38 tokens per session scan A 0a6d779f9a2f
cas-worker is a skill published in the GitHub repository codingagentsystem/cas (151 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,177 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.
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.
multi-search-engine
Use this skill when ordinary websearch is not enough and you need engine-specific public-web search strategy.