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/verify-docsnpx skills add YourTechBud/coding-harness-config --skill verify-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.00009 | $0.00791 |
| Opus 5 | $0.00005 | $0.00396 |
| Sonnet 5 | $0.00002 | $0.00158 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
verify-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
Review all documentation in docs/ and verify it against our conversation.
<verification_criteria>
- No contradictions: identify any statements in docs that conflict with or contradict what we discussed in this conversation.
- Self-explanatory: flag places where a reader would be confused without context they don't have — undefined terms, missing prerequisites, unclear steps, unstated assumptions.
- Nothing important missed: identify topics, decisions, or details from our conversation that should be documented but are absent or incomplete across docs/.
- Consolidation opportunities: identify duplication, redundancy, and excess verbosity across docs/. Suggest merges (files/sections/paragraphs/sentences), trims, or "single source of truth + links" improvements that increase findability without losing any details.
- Structure compliance: verify docs follow the repo docs architecture:
- Doc root is
docs/. - Required directories exist (even if empty):
docs/architecture/docs/journeys/docs/product/
docs/contains Markdown-only: no non-.mdfiles anywhere underdocs/.docs/README.mdis the single canonical index and must:- describe scope for
architecture/,journeys/,product/, plus any custom top-leveldocs/<dir>/present - list/link every file under
docs/excludingdocs/README.mditself - group links by top-level directory (include "Docs root (discouraged)" if any root-level docs exist)
- describe scope for
.mdfiles directly underdocs/(besidesdocs/README.md) are discouraged but allowed; call them out as a recommendation to move. </verification_criteria>
- Doc root is
- Produce a narrative verification report covering:
- What you reviewed (which files)
- Findings for each criterion (contradictions, clarity gaps, missing content)
- Findings for structure compliance (pass/fail + concrete issues + concrete fixes)
- Concrete suggested edits where issues are found (specific files and sections)
- Consolidation opportunities (specific, actionable merge/trim/link suggestions; include this section even if empty)
- An overall plain-language verdict
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 · 9 tokens per session scan A bacde3651fb8
verify-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 9 tokens to every session and 791 once invoked, about $0.0000 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…