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/urmzd/dotfiles/test-codenpx skills add urmzd/dotfiles --skill test-codegit clone --depth 1 https://github.com/urmzd/dotfilesWhat 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.00101 | $0.02625 |
| Opus 5 | $0.00051 | $0.01313 |
| Sonnet 5 | $0.00020 | $0.00525 |
| Haiku 4.5 | $0.00010 | $0.00263 |
Grade A, and why
test-code 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 yesterday.
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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Practices
Philosophy
Test your software, or your users will.
- Test against contracts, not implementations assert what it should do, not how it does it. Tests that break on every refactor are coupling to internals.
- State coverage > line coverage exercise meaningful paths and edge cases, not just lines. We intentionally use no coverage tools; percentage targets create false confidence.
- Tests are the first users of your API if tests are hard to write, the design is wrong. Refactor the interface, not the test.
- Property-based testing finds edges you didn't think of complement example-based tests with fuzz and property tests where the input space is large.
- Tests should be boring a test that's hard to read is a test nobody trusts. Inline data, obvious assertions, no clever abstractions.
See review-design for the underlying Pragmatic Programmer principles (design by contract, pragmatic paranoia).
Test Types
| Type | What It Verifies | When to Use | Codebase Example |
|---|---|---|---|
| Unit | Single function/module in isolation | Always. Every public function. | sr/crates/sr-core/src/version.rs. #[cfg(test)] mod tests |
| Integration | Multiple modules working together | Cross-layer interactions, real I/O | sr/crates/sr-git/tests/integration.rs. TempDir + real git CLI |
| Snapshot/Golden | Output hasn't changed unexpectedly | Templates, code generation, formatters | incipit/generators/golden_test.go. -update flag to regenerate |
| Fuzz | No panics/crashes on arbitrary input | Parsers, deserializers, sanitizers | incipit/resume/adapter_fuzz_test.go. Go native testing.F |
| Property-based | Invariants hold for generated inputs | Mathematical properties, roundtrip encode/decode | Use proptest (Rust), testing/quick (Go), hypothesis (Python) |
| Benchmark | Performance characteristics | Hot paths, algorithms, throughput | linear-gp/crates/lgp/benches/. criterion framework |
| Smoke | Basic environment sanity | CI gate, post-deploy check | linear-gp/crates/lgp/tests/smoke_tests.rs. 2 generations, no crash |
| E2E | Full system from user perspective | Critical user flows | teasr CI. real Chrome + xvfb-run dogfood |
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.
- yesterday First seen · 230 lines · 101 tokens per session scan A ce3c259ac0c8
test-code is a skill published in the GitHub repository urmzd/dotfiles (3 stars, last pushed 19d ago), licensed Apache-2.0. It adds 101 tokens to every session and 2,625 once invoked, about $0.0005 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
benchling-integration
Benchling Python SDK and REST API integration for registry entities, inventory, ELN entries, workflows, Benchling Apps, and Data Warehouse queries. Use when automating lab data with benchling-sdk or the v2 API.
astropy
Core Python library for astronomy and astrophysics workflows that need Astropy APIs, including units/quantities, coordinates, FITS I/O, tables, time systems, WCS, and cosmology. Use when implementing or debugging astronomical data analysis code with Astropy.
esm
Comprehensive toolkit for EvolutionaryScale protein language models including ESM3 (generative multimodal design across sequence, structure, and function) and ESM C (efficient embeddings). Use for protein sequence/structure/function tasks, inverse folding, embeddings, variant design, and ESMFold2 structure prediction…
mcp-notion-usage-guide
MCP Notion工具使用指南，包含常见问题解决方案和最佳实践。使用当： (1) 访问Notion数据库view URL出现"URL type view not currently supported"错误， (2) 需要获取数据库schema和表结构信息， (3) 查询数据库中的条目内容， (4) 创建页面时MULTISELECT字段值不存在导致失败， (5) 需要更新数据库schema添加新选项， (6) 开发需要集成Notion数据的自动化工作流， (7) querydatasources/query-database-view返回Business Plan要求错误， (8) 需要在无Business…
scan-commit
Automatically scan the repository for unstaged/untracked changes, group them into logical commits using hunk-level analysis, stage and commit them following Conventional Commits.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes.