execute

execute is a command for Claude Code from athola/claude-night-market. It costs 12 tokens per session (3,097 once invoked), scanned A, original, MIT.

An implementation command that follows a prepared plan in dependency order, records progress, and checks work at defined checkpoints.

In plain words
What is it for?
Use it to carry out planned tasks, work on a specific task or phase, resume from a checkpoint, and monitor progress through the implementation.
Why use it?
It turns a large plan into tracked tasks and helps reveal blockers or unmet acceptance criteria during development.

Command for Claude Code

Written for Claude Code: Claude Code plugin machinery. Also seen: mentions Claude Code.

Part of the attune plugin — 14 skills, 11 commands, 2 agents shipped together

Good fit Use it to carry out planned tasks, work on a specific task…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/athola/claude-night-market/execute
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.

Clone the repo
git clone --depth 1 https://github.com/athola/claude-night-market

Made for: Claude Code.

Or install attune, the plugin that ships this one along with the rest of its 14 skills, 11 commands, 2 agents.

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/commands/athola/claude-night-market/execute.svg)](https://agentmods.dev/commands/athola/claude-night-market/execute)
Your own site
<a href="https://agentmods.dev/commands/athola/claude-night-market/execute"><img src="https://agentmods.dev/badge/commands/athola/claude-night-market/execute.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,097 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.00012 $0.03097
Opus 5 $0.00006 $0.01548
Sonnet 5 $0.00002 $0.00619
Haiku 4.5 $0.00001 $0.00310

Measured 3d ago against content hash f6740f21d276, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 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.

plugins/attune/commands/execute.md · 523 lines

How it starts

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

Attune Execute Command

Execute implementation plans systematically with task tracking, checkpoint validation, and continuous progress reporting.

When To Use

Use this command when you need to:

  • Execute implementation plan with task tracking
  • Implement tasks in dependency order
  • Validate checkpoints against acceptance criteria
  • Track progress and identify blockers
  • Monitor velocity and burndown metrics
  • Ensure systematic quality-gated execution

When NOT To Use

Avoid this command if:

  • No implementation plan exists (use /attune:blueprint first)
  • Still planning or designing (complete planning phase)
  • Single isolated task (execute directly without framework)
  • Exploratory coding or quick prototype (too much overhead)

Usage

# Start execution from plan
/attune:execute

# Execute specific task
/attune:execute --task TASK-003

# Resume from checkpoint
/attune:execute --resume

# Execute specific phase
/attune:execute --phase "Phase 1"

What This Command Does

  1. Loads implementation plan from planning phase
  2. Invokes execution agent with superpowers integration
  3. Executes tasks in dependency order with checkpoints
  4. Tracks progress and updates task status
  5. Validates completion against acceptance criteria
  6. Reports progress with metrics and blockers

Integration with Superpowers

When superpowers plugin is available:

  • Uses Skill(superpowers:executing-plans) for systematic execution
  • Uses Skill(superpowers:systematic-debugging) for issue resolution
  • Uses Skill(superpowers:verification-before-completion) for validation

Without superpowers:

  • Falls back to attune's native execution agent
  • Provides similar checkpoint-based approach
  • Validates task completion systematically

Workflow

# 1. Load implementation plan
# Read docs/implementation-plan.md

# 2. Invoke execution agent
Agent(attune:project-implementer)

# 3. Execute tasks in dependency order:
#    For each task:
#      - Check dependencies complete
#      - Execute implementation
#      - Run tests
#      - Validate acceptance criteria
#      - Update progress tracker

# 4. Report progress
#    - Tasks completed/total
#    - Blockers and risks
#    - Next actions

# 5. Save execution state
#    - .attune/execution-state.json

Read the full file on GitHub · 523 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 · 523 lines · 12 tokens per session scan A f6740f21d276

Subscribe to this mod's changes

execute is a command published in the GitHub repository athola/claude-night-market (335 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 3,097 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.