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/implementation-planningnpx skills add thiientv/godmode --skill implementation-planninggit 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.00072 | $0.00401 |
| Opus 5 | $0.00036 | $0.00200 |
| Sonnet 5 | $0.00014 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
implementation-planning 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
Implementation Planning
Write for a capable engineer who does not know this repository or the hidden assumptions behind the request. A plan is useful only when another agent can execute it without reconstructing the design from hints.
Plan structure
Before listing tasks, record:
- goal and user-visible outcome;
- architecture and ownership boundaries;
- constraints, compatibility promises, and non-goals;
- files to create, modify, or delete;
- test and evidence strategy;
- rollback and migration safety.
Use plan-template.md for the complete skeleton.
Task rules
Break the work into thin, independently testable slices. Each task names:
- exact files and responsibilities;
- inputs, outputs, and interfaces consumed or produced;
- the failing or observable check first;
- the smallest implementation step;
- the focused command and expected result;
- the next checkpoint or integration dependency.
Prefer one behavior per task. Keep setup with the first deliverable that needs it. Do not create a task for speculative cleanup.
Plan quality gate
Before handing off:
- trace every design requirement to a task;
- search for placeholders such as
TBD,TODO, or “add appropriate…”; - check names and types across task boundaries;
- confirm commands exist in the repository;
- identify what the plan cannot prove locally.
Hand the completed plan to plan-execution or
subagent-driven-development. Do not claim the feature is implemented because
the plan is complete.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 57 lines · 72 tokens per session scan A c2233083636c
implementation-planning is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 7d ago), licensed MIT. It adds 72 tokens to every session and 401 once invoked, about $0.0004 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-задач вне автопилота.