What is execution-report?

A written report command that records what was implemented after a feature or fix is complete. It compares the finished work with the original plan and documents validation results, challenges, and differences.

Use it to document changed files, tests and other checks, successful approaches, difficulties, and any decisions that differed from the plan.

It preserves the reasoning and lessons from completed work instead of leaving them in temporary conversation history. This makes later review and process improvement easier.

How coleam00/Archon configures Claude Code

About the project

Archon is a workflow engine for AI coding agents that turns development processes into YAML-defined sequences with phases, validation gates, and artifacts. Developers use it to run repeatable processes such as planning, implementation, testing, code review, and pull-request creation across projects. The catalogue entries provide commands, agents, skills, hooks, instructions, and settings for working with Archon.

coleam00/Archon · 23,752 stars · on GitHub · archon.diy

Reuse

Borrowing it

Nothing to install: this file belongs to coleam00/Archon. 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/coleam00/Archon/dev/.claude/commands/validation/execution-report.md

Clone the repo

git clone --depth 1 https://github.com/coleam00/Archon

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/coleam00/archon/execution-report/github.svg)](https://agentmods.dev/commands/coleam00/archon/execution-report)

Your own site

<a href="https://agentmods.dev/commands/coleam00/archon/execution-report"><img src="https://agentmods.dev/badge/commands/coleam00/archon/execution-report/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/coleam00/archon/execution-report"><img src="https://agentmods.dev/badge/commands/coleam00/archon/execution-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 461 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.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.00461
Opus 5.5	$0.00003	$0.00184
Sonnet 5.5	$0.00001	$0.00092
Haiku 4.5	$0.00001	$0.00046

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

Security

Grade A, and why

execution-report 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 9d 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/commands/validation/execution-report.md · 78 lines

What it actually says

Execution Report

Review and deeply analyze the implementation you just completed.

Context

You have just finished implementing a feature or fix. Before moving on, reflect on:

What you implemented
How it aligns with the plan
What challenges you encountered
What diverged and why

Generate Report

Save to: .agents/execution-reports/[feature-name].md

Meta Information

Plan file: [path to plan that guided this implementation]
Feature: [brief description]
Files added: [list with full paths]
Files modified: [list with full paths]
Lines changed: +X -Y

Validation Results

Type Checking:  ✅/❌ [details if failed]
Linting:        ✅/❌ [details if failed]
Formatting:     ✅/❌ [details if failed]
Tests:          ✅/❌ [X passed, Y failed]

What Went Well

List specific things that worked smoothly:

[concrete examples from this implementation]

Challenges Encountered

List specific difficulties:

[what was difficult and why, with file:line references]

Divergences from Plan

For each divergence, document:

[Divergence Title]

Planned: [what the plan specified]
Actual: [what was implemented instead]
Reason: [why this divergence occurred]
Type: [Better approach found | Plan assumption wrong | Security concern | Performance issue | Package boundary constraint | Other]

Skipped Items

List anything from the plan that was not implemented:

[what was skipped]
Reason: [why it was skipped]

Archon-Specific Observations

Package boundaries respected: [yes/no — any cross-package concerns?]
Mock isolation: [any new mock.module() calls? Do they need separate test batches?]
Import patterns: [any tricky import situations?]

Recommendations

Based on this implementation, what should change for next time?

Plan command improvements: [suggestions]
Execute command improvements: [suggestions]
AGENTS.md additions: [suggestions]
.claude/rules/ updates: [suggestions]

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.

9d ago Changed · -1 lines 1ced19e82cb0
17d ago Changed 399a3c60eac1
1mo ago First seen · 79 lines · 7 tokens per session scan A 9baf9410ac82

Subscribe to this mod's changes

execution-report is a command published in the GitHub repository coleam00/Archon (23,752 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 461 once invoked, about $0.0000 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.

Writing and docs ai automation bun claude cli coding-assistant

Archon: Command for Claude Code