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 skills add NickCrew/Claude-Cortex --skill writing-plansgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nickcrew/claude-cortex/writing-plans)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/writing-plans"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/writing-plans.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.00487 |
| Opus 5 | $0.00014 | $0.00244 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
writing-plans 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 3d 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
/collaboration:writing-plans
Transforms brainstorm output into a concrete execution plan that cortex can enforce.
Inputs
- Brainstorm summary (see
/ctx:brainstorm). - Relevant workflows in
workflows/and rules inrules/Planning.md. - Any mandated modes (e.g.,
modes/Super_Saiyan.md,modes/Security_Audit.md).
Steps
- Restate Objective
- One paragraph referencing ticket/issue + constraints.
- Identify Workstreams
- Break work into 2–5 streams (frontend, backend, docs, infra, etc.).
- For each, list required agents/modes/rules.
- Define Tasks per Stream
- Bullet tasks with Definition of Done + validation (tests, lint, visual review).
- Include verification hooks (
rules/,commands/testing.yaml).
- Risk / Mitigation
- Capture open questions, dependencies, rollback steps.
- Task Sync
- For each bullet, create a Task TUI entry (press
T→A). - OR run
/ctx:execute-planafter this skill to auto-seed tasks (coming soon).
- For each bullet, create a Task TUI entry (press
Output template
## Objective
## Workstreams
### Stream 1 – <name>
- Task … (agent/mode/rule, validation)
- Task …
### Stream 2 – …
## Risks & Mitigations
- …
Store the plan in chat + docs/plans/<date>-<slug>.md if long-lived. Then move to /ctx:execute-plan.
Resources
- Plan template snippet:
skills/collaboration/writing-plans/resources/template.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 67 lines · 28 tokens per session scan A 715167a0a5ad
writing-plans is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 487 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-content-officer
Runs content as an operation — the production pipeline, editorial calendar, repurposing engine, competitive content intelligence, and audits of what already exists. Use this to build or fix a content production system, plan a calendar, decide how one piece becomes many, rank content ideas by expected impact, or audit…