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/nickcrew/claude-cortex/executing-plansnpx skills add NickCrew/Claude-Cortex --skill executing-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/executing-plans)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/executing-plans"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/executing-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.00050 | $0.00890 |
| Opus 5 | $0.00025 | $0.00445 |
| Sonnet 5 | $0.00010 | $0.00178 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade A, and why
executing-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 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Locks in an approved plan and drives it through cortex’s orchestration and verification stack, ensuring every item becomes a tracked task that is executed, verified, and reported.
When to Use This Skill
- A plan from
writing-plansor/ctx:planis ready for execution - Coordinating multiple workstreams or agents against a shared plan
- Ensuring plan items are tracked as tasks with status updates
- Running verification loops (tests, lint, visual checks) before marking tasks done
- Avoid using before a plan exists — use
writing-plansfirst
Prerequisites
- Plan output available in the thread (from
writing-plansor/ctx:plan) - Access to Task view (
T) in cortex TUI - Relevant modes and agents activated for the workstreams
Workflow
Step 1: Create and Sync Tasks
For each plan item, create or update a task in the Task view:
Task view (T) → Add (A) or Edit (E)
- Set category and workstream to mirror the plan’s stream names
- Ensure every plan item has a corresponding task — no orphan items
- Link tasks to the originating plan document
Step 2: Activate Modes and Rules
Toggle the required configuration to match the plan:
- Modes (view
3): Activate modes needed for current workstreams - Rules (view
4): Enable rules that apply (e.g., testing requirements, style enforcement)
Step 3: Execute Workstream Loops
For each task in priority order:
- Pick the next task from the active workstream
- Execute the work (implementation, writing, configuration, etc.)
- Verify before marking complete:
- Run tests:
pytest,vitest, or project-specific test command - Run linting:
just lintor equivalent - Visual check via Supersaiyan if UI changes are involved
- Run tests:
- Update task status and progress notes
# Example verification sequence
just test && just lint && echo "Verification passed"
Step 4: Update Stakeholders
For each completed workstream:
- Summarize progress and what’s next
- Attach relevant screenshots, logs, or test output
- Flag any blockers or scope changes discovered during execution
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.
- 2d ago First seen · 114 lines · 50 tokens per session scan A 450a1ac27bc1
executing-plans is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 890 once invoked, about $0.0003 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
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
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.
review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
aiox-review-story
QA gate for a story — verdict PASS/CONCERNS/FAIL/WAIVED + lifecycle transition. Use when: review story, qa gate, qa-gate, /review-story.
implementation-phase
Executes implementation tasks using Test-Driven Development, prevents code duplication through anti-duplication checks, and maintains quality through continuous testing. Use when implementing features from tasks.md, during the /implement phase, or when the user requests TDD-based implementation. (project).
xp-practices
Apply XP practices including pair programming, ensemble programming, continuous integration, and sustainable pace. Use when implementing agile development practices, improving team collaboration, or adopting technical excellence practices.