claudikins-kernel:execute

A command for carrying out a validated development plan using separate agents and isolated Git branches. It runs work in feature-sized batches, reviews the results in two stages, and pauses for human approval between batches.

In plain words
What is it for?
Use it to execute a prepared multi-task plan, resume or abort a run, inspect status, preview execution order, choose batch size or model, and view timing or execution details.
Why use it?
It keeps parallel work from interfering with itself and provides checkpoints for checking whether the work follows the plan and meets code-quality expectations.

Command

Part of the claudikins-kernel plugin — 4 skills, 4 commands, 8 agents, 8 hooks shipped together

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 commands/povvo/claudikins-kernel/execute
Clone the repo
git clone --depth 1 https://github.com/povvo/claudikins-kernel

Or install claudikins-kernel, the plugin that ships this one along with the rest of its 4 skills, 4 commands, 8 agents, 8 hooks.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,581 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00019 $0.04581
Opus 5 $0.00010 $0.02291
Sonnet 5 $0.00004 $0.00916
Haiku 4.5 $0.00002 $0.00458

Measured 3d ago against content hash 6f1a4a3b2c09, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

claudikins-kernel:execute scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

1. Get plan path from argument or find most recent in `.claude/plans/`
commands/execute.md · 736 lines

How it starts

The opening of the file, as written. The whole thing — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.

claudikins-kernel:execute Command

You are orchestrating a task execution workflow with isolated agents and human checkpoints between batches.

Flags

Flag Effect
--resume Resume from last checkpoint
--status Show current execution status
--abort Abort current execution (saves checkpoint)
--batch N Override batch size (default: from plan)
--model M Model for agents: opus or sonnet (default: opus)
--skip-review Skip code review (spec review still runs)
--dry-run Parse plan and show execution order without running
--timing Show task and batch durations
--trace Show execution trace at completion

Merge Strategy

None - task outputs are saved per-task, not merged.

Philosophy

"5-7 agents per SESSION, not 30 per batch. Features are the unit of work." - Boris

  • One task = one branch (isolation prevents pollution)
  • Fresh context per task (context: fork)
  • Two-stage review (spec compliance, then code quality)
  • Human checkpoints between batches (not individual tasks)
  • Commands own git (agents never checkout/merge/push)

Load Skill

First, load the git-workflow skill for methodology:

Skill(git-workflow)

This provides:

  • Task decomposition patterns
  • Review criteria and thresholds
  • Batch checkpoint decision trees
  • Circuit breaker and tracing patterns

State Management

State file: .claude/execute-state.json

{
  "session_id": "exec-YYYY-MM-DD-HHMM",
  "plan_source": "path/to/plan.md",
  "started_at": "ISO timestamp",
  "status": "initialising|executing|paused|completed|aborted",
  "current_batch": 1,
  "current_task": null,
  "tasks": [...],
  "batches": [...],
  "last_checkpoint": null
}

Read the full file on GitHub · 736 lines

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. 3d ago First seen · 736 lines · 19 tokens per session scan B 6f1a4a3b2c09

Subscribe to this mod's changes

claudikins-kernel:execute is a command published in the GitHub repository povvo/claudikins-kernel (126 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 4,581 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.