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 skills add tykisgod/quick-question --skill post-design-reviewgit clone --depth 1 https://github.com/tykisgod/quick-questionWrote 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/skills/tykisgod/quick-question/post-design-review)<a href="https://agentmods.dev/skills/tykisgod/quick-question/post-design-review"><img src="https://agentmods.dev/badge/skills/tykisgod/quick-question/post-design-review.svg" alt="Measured on agentmods" 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.00049 | $0.00472 |
| Opus 5 | $0.00024 | $0.00236 |
| Sonnet 5 | $0.00010 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
post-design-review 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 8d 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
Respond in the user's preferred language (detect from their recent messages, or fall back to the language setting in CLAUDE.md).
Review a game design document from an implementer's perspective.
Arguments: $ARGUMENTS (path to a design document, or empty to use the most recent design doc in Docs/qq/)
Process
- Find the document: if a path is given, read it. Otherwise, find the most recent
*_design.mdinDocs/qq/. - Spawn a review subagent using the Agent tool. The subagent should:
- Read design-reviewer-prompt.md for the full review checklist
- Read the design document
- Independently explore the codebase (Services, configs, existing design docs) to verify claims — do not rely solely on what the document says exists
- Output the review in the format specified in the reviewer prompt
- Verify the findings: as the main agent, independently spot-check the subagent's claims against the codebase. The subagent may misread code or reference stale information. For each finding, confirm or reject it with your own evidence before presenting to the user.
- Present the verified review to the user — only include findings you confirmed. Note any subagent findings you rejected and why.
- If verdict is HAS GAPS or NEEDS REWORK: revise the document together with the user. Re-run the subagent review after revisions. Loop until SOLID or the user explicitly accepts the gaps.
- If verdict is SOLID: confirm and recommend
/qq:plan. If invoked with--auto(or called from a skill running in--automode): runqq-execute-checkpoint.py pipeline-advance --project . --completed-skill "/qq:post-design-review" --next-skill "/qq:plan", then invoke/qq:plan --auto <document-path>.
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.
- 8d ago First seen · 23 lines · 49 tokens per session scan A 494de47dabef
post-design-review is a skill published in the GitHub repository tykisgod/quick-question (11 stars, last pushed 14d ago), licensed MIT. It adds 49 tokens to every session and 472 once invoked, about $0.0002 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
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.
security-architecture-review
Reviews a design or change for security before it ships — authentication and authorization, data handling, secrets, dependencies, and the secure-development practices around it. Use this to review an architecture or pull request for security, set secure coding standards, choose or tune SAST and DAST tooling, assess a…