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/0xbeycan/genesis/write-testsnpx skills add 0xBeycan/genesis --skill write-testsgit clone --depth 1 https://github.com/0xBeycan/genesisWhat 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.00053 | $0.00378 |
| Opus 5 | $0.00026 | $0.00189 |
| Sonnet 5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
write-tests 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
Write tests
When to use
Any time behavior changes — a new feature, a bug fix, a refactor that needs a
safety net. Test-first in both lanes: the failing test comes before the
code. An agent has no gut feeling for regressions; the test is its feedback
loop. See conventions.md §Testing.
Steps
- Find the behavior. What observable outcome or contract should hold? For a bug, reproduce it as a failing assertion first.
- Pick the level — unit / integration / e2e-contract, per the level guide
in
conventions.md§Testing. - Write the test against behavior, not implementation — assert outcomes
and contracts, not internals (adapter → contract test; rules in
conventions.md§Testing). - Watch it fail for the right reason (red) before writing the code.
- Implement the smallest change that makes it pass (green).
- Run the whole suite — no skipped or flaky tests left behind.
Notes
- The runner is stack-specific ({{TEST_RUNNER}} — chosen at bootstrap); its
command lives in
AGENTS.md§6 and.github/workflows/ci.yml. - Tests are part of the Definition of Done — run
review-own-diffandwrap-sessionbefore calling a change complete.
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 · 36 lines · 53 tokens per session scan A d106691d1456
write-tests is a skill published in the GitHub repository 0xBeycan/genesis (11 stars, last pushed 1mo ago), licensed MIT. It adds 53 tokens to every session and 378 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-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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.