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/create-review-guidenpx skills add YourTechBud/coding-harness-config --skill create-review-guidegit clone --depth 1 https://github.com/YourTechBud/coding-harness-configWrote 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/yourtechbud/coding-harness-config/create-review-guide)<a href="https://agentmods.dev/skills/yourtechbud/coding-harness-config/create-review-guide"><img src="https://agentmods.dev/badge/skills/yourtechbud/coding-harness-config/create-review-guide.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 | $0.00022 | $0.00810 |
| Opus 5 | $0.00011 | $0.00405 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
create-review-guide 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You generate a reviewer's orientation guide for a code change, so a human can review a large diff efficiently. This is a navigation aid, not a quality review — it does not judge or approve the code; it helps the reviewer build a mental model and know where to look.
Change scope
User-supplied scope:
$ARGUMENTS
If no user-supplied scope is provided, default to the current working tree changes
relative to HEAD, including staged, unstaged, and untracked files.
Goal
Produce a single self-contained HTML file under scratch/review/ that orients a
reviewer across two layers. Name the file after what the change is about, using a
short descriptive kebab-case slug (e.g. scratch/review/auth-token-refresh.html)
rather than a fixed name, so each guide is distinct and earlier guides are not
clobbered.
The guide covers two layers:
- Orientation — what this change is trying to achieve, and what a reviewer should therefore expect to change.
- Review walk — a module-by-module walk through the change. Start with a reading path overview: the affected modules in recommended reading order, each with a one-line reason. Then, for each module in that order, give its breakdown (expected logic, what is non-obvious or risky, what to verify) together with its files and focused notes on what to look at in each. End with a "Loose ends & miscellaneous" bucket for changed files that don't belong to a clean module (config, lockfiles, stray tweaks), so every changed file is still covered.
Success criteria
- A reviewer can build a mental model before reading any code, then read code to check whether it matches expectations.
- Logic is framed as expectations to test against the code, not conclusions to trust.
- Risky or non-obvious spots are called out with what to verify.
- It reads easily: plain, friendly language and short sentences, with repo jargon or technical terms defined briefly the first time they appear.
- The page is light and easy on the eyes, not a wall of text.
- A clear reading path is recommended; files live inside the module they belong to; every changed file is covered, including loose ends.
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.
- 3d ago First seen · 76 lines · 22 tokens per session scan A 06cf4d53c25d
create-review-guide is a skill published in the GitHub repository YourTechBud/coding-harness-config (5 stars, last pushed 4d ago), licensed Apache-2.0. It adds 22 tokens to every session and 810 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…