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.
npx agentmods add skills/thiientv/godmode/plan-executionnpx skills add thiientv/godmode --skill plan-executiongit clone --depth 1 https://github.com/thiientv/godmodeWhat 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 | $0.00068 | $0.00415 |
| Opus 5 | $0.00034 | $0.00208 |
| Sonnet 5 | $0.00014 | $0.00083 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
plan-execution 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 2d 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
Plan Execution
Treat the plan as an executable contract with room for evidence-backed corrections. Do not silently redesign it while implementing.
Before the first task
- Read the plan, referenced design, repository instructions, and current diff.
- Verify the starting branch, worktree, runtime, and baseline checks.
- Check that referenced files, commands, interfaces, and dependencies exist.
- Identify the first task whose result can invalidate the architecture.
Per-task loop
For each task:
- Restate the behavior and files in scope.
- Write or update the failing test/observation before implementation when the plan calls for behavior change.
- Run the focused check and confirm the failure is meaningful.
- Make the smallest change that satisfies the task.
- Run the focused check, then relevant neighboring checks.
- Inspect the diff for scope creep, accidental generated files, and contract drift.
- Record the result, evidence, and remaining limit before moving on.
If a test, dependency, or interface contradicts the plan, stop at a checkpoint and re-shape the affected task. Do not delete a check to make the plan green.
Integration discipline
- Keep each slice buildable when practical.
- Preserve the plan's public names unless an evidence-backed correction is approved.
- Run the broader suite after related slices stabilize.
- Use
completion-verificationfor the final claim.
Completion condition
Execution is complete when every in-scope task has a fresh result, the final diff matches the approved scope, and unverified surfaces are reported.
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.
- 2d ago First seen · 52 lines · 68 tokens per session scan A 060c170c619f
plan-execution is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 7d ago), licensed MIT. It adds 68 tokens to every session and 415 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.