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/core_piv_loop/execute.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/execute)<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/execute"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/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.
<a href="https://agentmods.dev/commands/thesmokedev/taskchad-os/execute"><img src="https://agentmods.dev/badge/commands/thesmokedev/taskchad-os/execute.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.00004 | $0.00480 |
| Opus 5.5 | $0.00002 | $0.00192 |
| Sonnet 5.5 | $0.00001 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute: Implement from Plan
Plan to Execute
Read plan file: $ARGUMENTS
Execution Instructions
1. Read and Understand
- Read the ENTIRE plan carefully
- Understand all tasks and their dependencies
- Note the validation commands to run
- Review the testing strategy
2. Execute Tasks in Order
For EACH task in "Step by Step Tasks":
a. Navigate to the task
- Identify the file and action required
- Read existing related files if modifying
b. Implement the task
- Follow the detailed specifications exactly
- Maintain consistency with existing code patterns
- Include proper type hints and documentation
- Add structured logging where appropriate
c. Verify as you go
- After each file change, check syntax
- Ensure imports are correct
- Verify types are properly defined
3. Implement Testing Strategy
After completing implementation tasks:
- Create all test files specified in the plan
- Implement all test cases mentioned
- Follow the testing approach outlined
- Ensure tests cover edge cases
4. Run Validation Commands
Execute ALL validation commands from the plan in order:
# Run each command exactly as specified in plan
If any command fails:
- Fix the issue
- Re-run the command
- Continue only when it passes
5. Final Verification
Before completing:
- ✅ All tasks from plan completed
- ✅ All tests created and passing
- ✅ All validation commands pass
- ✅ Code follows project conventions
- ✅ Documentation added/updated as needed
Output Report
Provide summary:
Completed Tasks
- List of all tasks completed
- Files created (with paths)
- Files modified (with paths)
Tests Added
- Test files created
- Test cases implemented
- Test results
Validation Results
# Output from each validation command
Ready for Commit
- Confirm all changes are complete
- Confirm all validations pass
- Ready for
/commitcommand
Notes
- If you encounter issues not addressed in the plan, document them
- If you need to deviate from the plan, explain why
- If tests fail, fix implementation until they pass
- Don't skip validation steps
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 · 102 lines · 4 tokens per session scan A 48e069ae8360
execute is a command published in the GitHub repository TheSmokeDev/taskchad-os (28 stars, last pushed 23d ago), licensed MIT. It adds 4 tokens to every session and 480 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
second-brain-mapping
Map your vault: extract structured metadata from every typed file, surface cross-doc insights, optionally build a knowledge graph.
cierre
A sales call just ended: turn its transcript into the full follow-up (CRM, tasks, email draft, reminder, coaching).
daily-journal
Daily journal interview and entry creator with emotional floor tagging.
deconstruct
First-principles analyst: surface hidden assumptions, find foundational truths, rebuild from scratch.
diagnose
Run a self-check on your AI Brain Starter install (CLAUDE.md, Meta folder, skills, hooks, MCPs).
evolve
Cluster hardened instincts into a proposed Command / Skill / Agent (Instinct Engine).