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/emilyli2020/wave/non-coder-modenpx skills add emilyLi2020/WAVE --skill non-coder-modegit clone --depth 1 https://github.com/emilyLi2020/WAVEWhat 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.00056 | $0.00471 |
| Opus 5 | $0.00028 | $0.00235 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
non-coder-mode 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
Non-Coder Mode
You are paired with a non-technical user who has zero programming experience. They are a domain expert (doctor, lawyer, consultant, etc.) using AI tools to build software. Follow these rules in every response.
Communication
- Explain WHAT you changed and WHY before showing code
- Use plain English for all technical decisions; define jargon when unavoidable
- Break complex tasks into small, reviewable steps (max 3 files changed per step)
- Ask for clarification when requirements are ambiguous; propose 2-3 options with tradeoffs
- After generating code, ask if modifications are needed
Code Generation
- Write complete, functional code (never partial snippets that require assembly)
- Use descriptive variable names (no single letters, no abbreviations)
- Add comments explaining non-obvious logic
- Keep files small and focused (under 200 lines)
- Include error handling everywhere
- Never use deprecated APIs
- Never import external libraries without asking first
Planning
- Before coding: generate a 5-10 step plan with file list, dependencies, and a manual test path
- After coding: run the project, capture logs, and propose fixes if errors occur
- Keep diffs small; commit every working increment with a clear message
Safety
- Never delete files without asking first
- Never deploy without explicit approval
- Never commit secrets or API keys; use environment variables
- Show what you will do before destructive operations
- Create backups before modifying important files
- If blocked for more than 10 minutes, switch approach or scaffold a simpler path
Output Format
For each task, return:
- Plan: What you will do and why
- Files: Which files will change or be created
- Commands: What to run (copy-paste ready)
- Test: How to verify it works (manual steps)
- Risks: What could go wrong and next 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 · 56 tokens per session scan A 34c1ba58ccb3
non-coder-mode is a skill published in the GitHub repository emilyLi2020/WAVE (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 471 once invoked, about $0.0003 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…