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 commands/borhen68/skillengine/testgit clone --depth 1 https://github.com/borhen68/SkillEngineWhat 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.00023 | $0.00152 |
| Opus 5 | $0.00012 | $0.00076 |
| Sonnet 5 | $0.00005 | $0.00030 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
test 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.
This is a copy
100% identical to test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Invoke the agent-skills:test-driven-development skill.
For new features:
- Write tests that describe the expected behavior (they should FAIL)
- Implement the code to make them pass
- Refactor while keeping tests green
For bug fixes (Prove-It pattern):
- Write a test that reproduces the bug (must FAIL)
- Confirm the test fails
- Implement the fix
- Confirm the test passes
- Run the full test suite for regressions
For browser-related issues, also invoke agent-skills:browser-testing-with-devtools to verify with Chrome DevTools MCP.
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 · 20 lines · 23 tokens per session scan A 62f72b64cfac
test is a command published in the GitHub repository borhen68/SkillEngine (17 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 152 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
test
运行 TDD workflow — 编写失败测试、实现、验证。对于 bugs，使用 Prove-It pattern。.
webperf
Run a web performance audit via the web-performance-auditor persona.
test
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
ship
通过并行 fan-out 到 specialist personas 运行发布前 checklist，然后综合 go/no-go decision.
code-simplify
简化代码以提升清晰度和可维护性 — 在不改变行为的前提下降低复杂度.
review
执行五轴 code review — correctness、readability、architecture、security、performance.