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/solution-designnpx skills add thiientv/godmode --skill solution-designgit 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.00075 | $0.00554 |
| Opus 5 | $0.00037 | $0.00277 |
| Sonnet 5 | $0.00015 | $0.00111 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
solution-design 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solution Design
Make the problem concrete before choosing the solution. The goal is shared understanding, not a long ceremony.
Classify the request
- Spike: the output is a recommendation or feasibility result; keep any prototype disposable.
- Bounded: an existing flow is understood and the change is narrow; use a short design and one approval gate.
- Architectural: the request creates a subsystem, changes a public contract, or has several independent surfaces; write a design artifact.
When uncertain, choose the heavier path until discovery proves otherwise.
Explore in order
- Read repository instructions, nearby code, tests, and recent changes.
- Separate observed facts from assumptions and unknowns.
- Ask only the questions that change scope, safety, data shape, or user outcome. Ask one focused question at a time when a conversation is needed.
- State the outcome, users, constraints, non-goals, acceptance evidence, and principal risks.
- Compare two or three viable approaches when the choice is material. Explain the trade-off and recommend the smallest safe option.
- Present the design at the depth the request requires. Get approval before consequential implementation when the user has not already authorized it.
Use discovery-questions.md when the brief has unclear goals or competing stakeholders.
Design artifact
For architectural work, save a concise design under the repository's normal docs location. Include:
Problem and users
Outcome and non-goals
Constraints and assumptions
Options considered and recommendation
Interfaces and data affected
Failure modes and rollback
Acceptance evidence
Open decisions
Do not start implementation while a decision that materially changes the public behavior, data model, or safety boundary is unresolved.
Handoff
- Hand an approved multi-step design to
implementation-planning. - Hand a concrete failure to
root-cause-debugging. - Add a domain skill only when its expertise changes the design.
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 · 74 lines · 75 tokens per session scan A bdce32deccbd
solution-design is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 7d ago), licensed MIT. It adds 75 tokens to every session and 554 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-задач вне автопилота.