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/yourtechbud/coding-harness-config/plan-docsnpx skills add YourTechBud/coding-harness-config --skill plan-docsgit clone --depth 1 https://github.com/YourTechBud/coding-harness-configWhat 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.00010 | $0.00601 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
plan-docs 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
You are planning documentation updates. The user has provided guidance on what to document.
<doc_guidance> $ARGUMENTS </doc_guidance>
<planning_steps>
-
Explore the current docs before planning:
- Inventory
docs/if it exists, including files and top-level directories. - Understand existing style, naming, placement, structure, and navigation.
- Identify duplication, stale organization, excessive root-level files, or unclear ownership only when relevant to the requested docs work.
- If
docs/engineering-guidance/exists, treat it as protected: acknowledge it in navigation planning but do not plan modifications inside it unless explicitly requested.
- Inventory
-
Plan the smallest useful documentation change:
- Prefer updating or consolidating existing docs when it improves findability or reduces duplication without losing details.
- Create new docs only when the topic needs a durable home or does not fit existing files.
- Preserve existing structure unless a structural change has clear value. Suggest moves, renames, merges, or new folders only when they materially improve navigation, reduce duplication, or clarify ownership.
- Root-level docs files are fine, but many unrelated ones suggest a clearer structure may help.
- Prefer minimal diffs; avoid rewriting unrelated sections.
- Recommend structure that fits this repo; do not force universal folders like
architecture/,journeys/, orproduct/. - Plan
docs/README.mdupdates when navigation or structure changes. Treat it as explaining how docs are organized, not just a flat index. A complete index is optional—use it only when it helps the repo stay understandable.
-
Output the full plan in chat with:
- Brief goal summary.
- Current docs observations that affected the plan.
- Files to create, with proposed purpose and headings/sections.
- Files to edit, with exact sections to add, revise, move, or trim.
docs/README.mdchanges, if any.- Structure changes, if any, with rationale.
- Major diffs to confirm: moves, renames, deletes, cross-file merges, or large restructures. Note how details will be preserved in any consolidation.
- Open questions that block execution.
-
End by inviting the user to revise the plan or approve implementation.
</planning_steps>
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 · 51 lines · 10 tokens per session scan A 0846a30958be
plan-docs is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 10 tokens to every session and 601 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…