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/zate/cc-plugins/plan-managementnpx skills add Zate/cc-plugins --skill plan-managementgit clone --depth 1 https://github.com/Zate/cc-pluginsWhat 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.00037 | $0.01223 |
| Opus 5 | $0.00018 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
plan-management 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Management
Conventions for .devloop/plan.md file format and updates.
Plan Location
Primary: .devloop/plan.md
Plan Format
# Devloop Plan: [Feature Name]
**Created**: YYYY-MM-DD
**Updated**: YYYY-MM-DD HH:MM
**Status**: Planning | In Progress | Complete
**Issue**: #123 (https://github.com/owner/repo/issues/123) (optional, if started from GH issue)
**Branch**: feat/feature-name (optional)
**PR**: https://github.com/.../pull/123 (after PR created)
## Overview
Brief description of the plan.
## Phase 1: [Phase Name]
- [ ] Task 1.1: Description
- Acceptance: Criteria
- Files: Expected files
## PR Feedback (after review)
PR #123 - @reviewer (CHANGES_REQUESTED)
### Blockers
- [ ] [PR-123-1] Fix issue (@reviewer)
### Suggestions
- [ ] [PR-123-2] Consider alternative (@reviewer)
## Progress Log
- [timestamp]: Event
Task Markers
| Marker | Meaning |
|---|---|
- [ ] |
Pending |
- [x] |
Completed |
- [~] |
In progress |
- [!] |
Blocked |
PR Feedback Task IDs
Format: [PR-{number}-{item}]
Example: [PR-123-1] = First feedback item from PR #123
Model Hint Markers
Annotate tasks with model selection for optimized execution:
| Marker | When to Use | Examples |
|---|---|---|
[model:haiku] |
Simple, mechanical, low-reasoning | Writing tests from patterns, docs, formatting, linting, config changes, file renames |
[model:sonnet] |
Complex reasoning, multi-file coordination | Architecture, debugging, multi-file refactoring, security analysis, performance |
| (no annotation) | Orchestrator does inline | Single-line edits, running a command, status checks |
Place at the end of the task line:
- [ ] Task 1.1: Write unit tests for UserService [model:haiku]
- [ ] Task 1.2: Refactor authentication middleware [model:sonnet]
- [ ] Task 1.3: Update version in package.json
Parallelism Markers
[parallel:A]- Can run concurrently with other Group A tasks[parallel:B]- Can run concurrently with other Group B tasks (etc.)[depends:N.M]- Must wait for Task N.M to complete first
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 · 160 lines · 37 tokens per session scan A 3907e17d5042
plan-management is a skill published in the GitHub repository Zate/cc-plugins (10 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,223 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.