executing-plans

executing-plans is a skill for Claude Code, Codex from NickCrew/Claude-Cortex. It costs 50 tokens per session (890 once invoked), scanned A, original, MIT.

A workflow for carrying an approved plan through tracked tasks, coordinated work, and verification checks.

In plain words
What is it for?
Use it to sync plan items into a task system, coordinate workstreams or agents, and run tests, lint checks, or visual reviews.
Why use it?
It keeps planned work visible and helps ensure tasks are tested, reviewed, and reported before completion.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to sync plan items into a task system, coordinate workstreams or agents, and run tests, lint checks, or visual reviews.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nickcrew/claude-cortex/executing-plans
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.

Any agent
npx skills add NickCrew/Claude-Cortex --skill executing-plans
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for executing-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/nickcrew/claude-cortex/executing-plans/github.svg)](https://agentmods.dev/skills/nickcrew/claude-cortex/executing-plans)
Your own site
<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/executing-plans"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/executing-plans/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for executing-plans

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 890 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00050 $0.00890
Opus 5.5 $0.00020 $0.00356
Sonnet 5.5 $0.00010 $0.00178
Haiku 4.5 $0.00005 $0.00089

Measured 1mo ago against content hash 450a1ac27bc1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/collaboration/executing-plans/SKILL.md · 114 lines

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-plans or /ctx:plan is 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-plans first

Prerequisites

  • Plan output available in the thread (from writing-plans or /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:

  1. Pick the next task from the active workstream
  2. Execute the work (implementation, writing, configuration, etc.)
  3. Verify before marking complete:
    • Run tests: pytest, vitest, or project-specific test command
    • Run linting: just lint or equivalent
    • Visual check via Supersaiyan if UI changes are involved
  4. 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

Read the full file on GitHub · 114 lines

Files

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.

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. 1mo ago First seen · 114 lines · 50 tokens per session scan A 450a1ac27bc1

Subscribe to this mod's changes

executing-plans is a skill published in the GitHub repository NickCrew/Claude-Cortex (62 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 890 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories