aspens: Agent for Claude Code

.claude/agents/execute.md

execute is an agent for Claude Code from aspenkit/aspens. It costs 24 tokens per session (1,343 once invoked), scanned A, original, MIT.

A development agent that carries out an existing coding plan by assigning work to subagents, running tests, and preparing the result for delivery.

In plain words
What is it for?
Use it to implement planned features, divide work into phases, verify changes with tests, and complete development tasks.
Why use it?
It handles the execution stage after a plan has already been written, so implementation work follows an agreed sequence.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; reads .claude/ paths; mentions CLAUDE.md.

This is aspenkit/aspens's own configuration. It tells Claude Code how to work on aspens itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aspens configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aspenkit/aspens. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/aspenkit/aspens/main/.claude/agents/execute.md
Clone the repo
git clone --depth 1 https://github.com/aspenkit/aspens

Made for: Claude Code.

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 execute

README.md
[![agentmods](https://agentmods.dev/badge/agents/aspenkit/aspens/execute/github.svg)](https://agentmods.dev/agents/aspenkit/aspens/execute)
Your own site
<a href="https://agentmods.dev/agents/aspenkit/aspens/execute"><img src="https://agentmods.dev/badge/agents/aspenkit/aspens/execute/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 execute

Your own site · 80×15
<a href="https://agentmods.dev/agents/aspenkit/aspens/execute"><img src="https://agentmods.dev/badge/agents/aspenkit/aspens/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,343 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.00024 $0.01343
Opus 5.5 $0.00010 $0.00537
Sonnet 5.5 $0.00005 $0.00269
Haiku 4.5 $0.00002 $0.00134

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

Security

Grade A, and why

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

.claude/agents/execute.md · 110 lines

How it starts

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

You are an execution agent. You execute development plans created by the plan agent. You do NOT create or modify plans.

Tech stack: Node.js 20+ (pure ESM) | Commander | Vitest | es-module-lexer | @clack/prompts | picocolors

Your job: Read the plan, spawn executor subagents for each task, verify results, and ship.

Key Conventions

  • Pure ESM — use import/export; never require(). Package uses "type": "module" throughout.
  • CliError pattern — command handlers throw CliError from src/lib/errors.js; never call process.exit() directly. Top-level handling lives in bin/cli.js.
  • es-module-lexer WASM — must await init before calling parse() in graph-builder.
  • Path sanitization — parseFileOutput() restricts writes to .claude/ and CLAUDE.md; never bypass this. Accepts allowedPaths override for multi-target.
  • Target/Backend distinction — target = output format/location; backend = which LLM CLI generates content. Config lives in .aspens.json.

Step 0 — Load plan

  1. Find the plan:
    • If the user provides a task name → read dev/active/{task-name}/plan.md
    • If no task name → list dev/active/ directories. If exactly one exists, use it. If multiple, ask the user which one.
    • If no plan file exists → tell the user to run the plan agent first, then stop. Do not improvise a plan.
  2. Check the plan's verdict line for scope (trivial/small/medium/large). This determines execution behavior.

Step 1 — Execute

For each phase, spawn executor subagents for each task. Tasks within a phase run in parallel.

Each task in the plan has a model tag (haiku or sonnet). Use the tagged model when spawning.

Spawning an executor:

Use the Agent tool:
  prompt: |
    You are executing a single task from a development plan.

    TASK: {task description from plan}
    FILES: {specific files to modify}
    CONTEXT: {relevant code-map entries or brief architectural notes — NOT full file contents}
    CONVENTIONS: Read CLAUDE.md and .claude/skills/base/skill.md for project conventions before writing code. Pure ESM only (import/export, never require). Throw CliError instead of process.exit().

    Instructions:
    1. Read the files you need to modify
    2. Make the changes described in the task
    3. Run `npm test` to verify changes

    Return ONLY this summary (nothing else):
    - task: {task name}
    - files: {files changed, comma-separated}
    - tests: pass | fail | none
    - issues: {any problems encountered, or "none"}
  model: {haiku or sonnet, per task tag}

Read the full file on GitHub · 110 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. 1mo ago First seen · 110 lines · 24 tokens per session scan A dddcef24fb6e

Subscribe to this mod's changes

execute is an agent published in the GitHub repository aspenkit/aspens (103 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 1,343 once invoked, about $0.0001 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-08-30.

Related

Other agents, from other repositories

sw-closer

Closes a SpecWeave increment in a fresh context - ledger check, verify, optional review, complete. Use after the implementing session finishes, to keep closure out of a bloated context.

anton-abyzov/specweave · 44 tokens

adversarial-reviewer

Independent adversarial reviewer for a code change. Assumes the implementation is WRONG until a reproduction proves otherwise, attacking the documented invariants and the tests that pin them. Produces a findings JSON the gate records and enforces. Never fixes the implementation and never sees the author's reasoning …

jakubsuplicki/codument · 67 tokens

code-reviewer

Reviews a single feature's source files for bugs, security issues, performance problems, and code quality concerns. Reports findings by severity. Does NOT make breaking changes — only safe, non-breaking fixes.

jakubsuplicki/codument · 43 tokens

doc-scanner

Scans a codebase to identify features, modules, and documentation gaps. Maps the project structure and determines which source files belong to which features. Use for bootstrap scanning of undocumented projects.

jakubsuplicki/codument · 41 tokens

adversarial-planner

Independent adversary for an implementation PLAN, before any code is written. Attacks the written plan's scope, non-goals, and decisions against the committed constraints it must honor, and surfaces only grounded objections for the human to decide. Never rewrites the plan and never sees the author's reasoning …

jakubsuplicki/codument · 82 tokens

doc-writer

Creates and updates feature documentation by reading source code and writing real documentation content. Invoke with specific instructions about which doc to create/update and which source files to read.

jakubsuplicki/codument · 36 tokens