Borrowing it
Nothing to install: this file belongs to TheSmokeDev/taskchad-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSmokeDev/taskchad-os/master/.claude/commands/validation/execution-report.mdgit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/execution-report)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/execution-report"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/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.
<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/execution-report"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/execution-report.svg" alt="Reviewed on agentmods" width="80" 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.00006 | $0.00372 |
| Opus 5.5 | $0.00002 | $0.00149 |
| Sonnet 5.5 | $0.00001 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
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 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.
What it actually says
Execution Report
Review and deeply analyze the implementation you just completed.
Context
You have just finished implementing a feature. 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]
- Files added: [list with paths]
- Files modified: [list with paths]
- Lines changed: +X -Y
Validation Results
- Syntax & Linting: ✓/✗ [details if failed]
- Type Checking: ✓/✗ [details if failed]
- Unit Tests: ✓/✗ [X passed, Y failed]
- Integration Tests: ✓/✗ [X passed, Y failed]
What Went Well
List specific things that worked smoothly:
- [concrete examples]
Challenges Encountered
List specific difficulties:
- [what was difficult and why]
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 | Other]
Skipped Items
List anything from the plan that was not implemented:
- [what was skipped]
- Reason: [why it was skipped]
Recommendations
Based on this implementation, what should change for next time?
- Plan command improvements: [suggestions]
- Execute command improvements: [suggestions]
- CLAUDE.md additions: [suggestions]
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.
- 1mo ago First seen · 72 lines · 6 tokens per session scan A 43d0d805a578
execution-report is a command published in the GitHub repository TheSmokeDev/taskchad-os (28 stars, last pushed 23d ago), licensed MIT. It adds 6 tokens to every session and 372 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.
Other commands, from other repositories
report
Persist a meaningful worker report for durable delivery to the active project orchestrator.
obsidian-board-hygiene
Bulk-triage a kanban board - surface stale items and archive, reschedule, or mark them done in one pass.
talent-psych-safety
Measure psychological safety on a team using Edmondson's 7-question scale (anonymous, longitudinal, team-by-team) plus interpretation rubric and intervention design. Cites Project Aristotle. Refuses "psychological safety training" as primary intervention without leader behavior change. Refuses single-snapshot scoring.…
talent-retention
Retention architecture for a high-performer cohort. Stay-interview script (the practitioner's voice), per-person leverage analysis (1-2 changes that would make this person 5x more likely to stay another 24 months), aggregate pattern across the cohort, system redesign recommendations. Cites stay-interview research…
talent-team-dynamics
Audit a team's dynamics. Hackman criteria check (real team or co-acting group?), Tuckman stage, status-hierarchy map, interdependence map, communication-pattern analysis. Refuses generic "team-building exercises" without diagnostic first. Names which Hackman criterion fails when one does — clarify…
culture-values-ops
Operationalize declared values into systems. For each value, build the matrix — hire criteria, promote criteria, celebration triggers, fire criteria, measurement metric, pay structure — and run the operational test (can an outsider deduce this value from these systems alone?). Refuses values-as-aspiration; insists on…