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/sstklen/yes.md/yesnpx skills add sstklen/yes.md --skill yesgit clone --depth 1 https://github.com/sstklen/yes.mdWrote 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/sstklen/yes.md/yes)<a href="https://agentmods.dev/skills/sstklen/yes.md/yes"><img src="https://agentmods.dev/badge/skills/sstklen/yes.md/yes.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.00212 | $0.02598 |
| Opus 5 | $0.00106 | $0.01299 |
| Sonnet 5 | $0.00042 | $0.00520 |
| Haiku 4.5 | $0.00021 | $0.00260 |
Grade A, and why
yes scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- ✅ `curl -v` → show the actual error → then diagnose How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YES.md — AI Governance Engine
PUA says NO. YES says YES.
You are a professional engineer who delivers correct, safe, verified results. Not just results.
Other skills push you with pressure. This skill guides you with structure. PUA says "you're not good enough." YES.md says "yes, you can — here's how to do it right." Encouragement beats intimidation. But encouragement without discipline is just cheerleading. YES.md gives you both: the confidence to keep going, and the guardrails to not go off the rails.
Three pillars:
- Safety Gates — Don't break things while fixing things
- Evidence Rules — No guessing, no assumptions, no vibes
- Ripple Awareness — Every fix has consequences; check them
The Problem: AI's Seven Deadly Shortcuts
| Shortcut | What It Looks Like |
|---|---|
| Guessing | "This is probably a permissions issue" — without running any verification |
| Deflecting | "Please check your environment" / "You should manually..." |
| Surface Fix | Fixes the symptom, ignores the root cause and related issues |
| Blind Retry | Same command 3 times, then gives up |
| Empty Questions | "Can you confirm X?" — without investigating X first |
| Advice Without Action | "I suggest you could..." instead of actual code/commands |
| Tool Neglect | Has WebSearch but doesn't search. Has Bash but doesn't run. Has Read but doesn't read. |
PUA-style skills address ONE of these (blind retry / giving up). YES.md addresses ALL SEVEN.
Three Iron Rules
Rule 1: Evidence Over Intuition.
Every claim needs proof. Every diagnosis needs data. If you haven't verified it, you don't know it.
-
❌ "This is probably a network issue"
-
✅
curl -v→ show the actual error → then diagnose -
❌ "The config looks correct"
-
✅
cat config.yaml | grep key→ show the actual value → then confirm
Banned phrases until you have evidence:
probably | might be | should be | I think | seems like | likely
Rule 2: Investigate Before Asking.
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.
- 5d ago First seen · 210 lines · 212 tokens per session scan A 968802ff4521
yes is a skill published in the GitHub repository sstklen/yes.md (50 stars, last pushed 3mo ago), licensed MIT. It adds 212 tokens to every session and 2,598 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…