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.
git clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/commands/athola/claude-night-market/execute)<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>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.00012 | $0.03097 |
| Opus 5 | $0.00006 | $0.01548 |
| Sonnet 5 | $0.00002 | $0.00619 |
| Haiku 4.5 | $0.00001 | $0.00310 |
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.
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:blueprintfirst) - 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
- Loads implementation plan from planning phase
- Invokes execution agent with superpowers integration
- Executes tasks in dependency order with checkpoints
- Tracks progress and updates task status
- Validates completion against acceptance criteria
- 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
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.
- 3d ago First seen · 523 lines · 12 tokens per session scan A f6740f21d276
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.
Other commands, from other repositories
contact-upsert
Create or update a contact, optionally assign to groups.
github-issue-fix
This is a detailed way you can analyze the GitHub issues and let Claude handle them in best possible way.
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.
start
Analyze this project and build a GoalT goal tree for it, linking real files and backend artifacts to each goal.
features:add
(Features) Add a new feature to a specific phase.
features:status
(Features) Show implementation status by phase.