Borrowing it
Nothing to install: this file belongs to xigua-wang/skill-doctor. 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/xigua-wang/skill-doctor/main/.codex/skills/technical-plan-guard/SKILL.mdgit clone --depth 1 https://github.com/xigua-wang/skill-doctorWrote 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/xigua-wang/skill-doctor/technical-plan-guard)<a href="https://agentmods.dev/skills/xigua-wang/skill-doctor/technical-plan-guard"><img src="https://agentmods.dev/badge/skills/xigua-wang/skill-doctor/technical-plan-guard/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/skills/xigua-wang/skill-doctor/technical-plan-guard"><img src="https://agentmods.dev/badge/skills/xigua-wang/skill-doctor/technical-plan-guard.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.00072 | $0.00469 |
| Opus 5 | $0.00036 | $0.00234 |
| Sonnet 5 | $0.00014 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
technical-plan-guard 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 10d 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
Technical Plan Guard
For this repository, any new requirement should start with a technical plan document under docs/ before implementation work begins.
When to use
Use this skill when the user:
- asks to add a new feature or workflow
- changes product or technical direction
- requests a non-trivial refactor
- asks for a new skill, rule, or repository convention
Skip this skill only for:
- typo or wording fixes
- trivial one-line bug fixes
- purely exploratory questions with no requested change
Required output
Create a technical plan file in docs/ with this filename pattern:
docs/tech-plan-<topic>-<YYYYMMDD>-session-<session-id>.md
Rules:
- use lowercase kebab-case for
<topic> - keep
<topic>short and specific, usually 2 to 6 words - use the current local date in
YYYYMMDD - keep the literal segment
session - use a short session identifier in
<session-id>, such as001,alpha, ornew-skill
Example:
docs/tech-plan-new-skill-doc-rule-20260417-session-001.md
Working procedure
- Infer a concise topic from the request.
- Pick a session id that distinguishes the planning round.
- Create the new plan file from
docs/technical-plan-template.mdif available. - Fill in scope, constraints, implementation steps, risks, and validation.
- Only then proceed with code or content changes needed by the request.
Plan content
The plan should cover:
- background
- goal and non-goals
- proposed approach
- file or module impact
- risks and tradeoffs
- validation steps
If the repository already contains a broader strategy document such as docs/technical-plan.md, treat it as context, not as the per-request plan file.
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.
- 10d ago First seen · 63 lines · 72 tokens per session scan A e6e5e2757a46
technical-plan-guard is a skill published in the GitHub repository xigua-wang/skill-doctor (272 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 469 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…