cas-task-tracking

A system for recording development tasks in a shared task list that persists between sessions.

In plain words
What is it for?
Use it to create, start, update, prioritize, link, review, and close tasks, including work assigned across multiple coding agents.
Why use it?
It keeps priorities, dependencies, progress notes, and blocked work from being lost when a session ends.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/codingagentsystem/cas/cas-task-tracking
Any agent
npx skills add codingagentsystem/cas --skill cas-task-tracking
Clone the repo
git clone --depth 1 https://github.com/codingagentsystem/cas

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 309 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00309
Opus 5 $0.00018 $0.00154
Sonnet 5 $0.00007 $0.00062
Haiku 4.5 $0.00004 $0.00031

Measured yesterday against content hash 1e847f45b13e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cas-task-tracking 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.

.claude/skills/cas-task-tracking/SKILL.md · 28 lines

What it actually says

CAS Task Tracking

Use mcp__cas__task instead of built-in TodoWrite. CAS tasks persist across sessions.

Core Workflow

  1. Create: mcp__cas__task action=create title="..." description="..." priority=2
  2. Start: mcp__cas__task action=start id=<task-id>
  3. Progress: mcp__cas__task action=notes id=<task-id> notes="..." note_type=progress
  4. Close: mcp__cas__task action=close id=<task-id> reason="..."

Useful Actions

  • Ready tasks: mcp__cas__task action=ready — unblocked, actionable work
  • My tasks: mcp__cas__task action=mine — tasks assigned to you
  • Blocked: mcp__cas__task action=list status=blocked
  • Add dependency: mcp__cas__task action=dep_add id=<task> to_id=<blocker> dep_type=blocks

Note Types

progress, blocker, decision, discovery — use the right type so notes are meaningful in context.

Changes

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.

  1. yesterday First seen · 28 lines · 37 tokens per session scan A 1e847f45b13e

Subscribe to this mod's changes

cas-task-tracking is a skill published in the GitHub repository codingagentsystem/cas (151 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 309 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.