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/machbuilds/atom/test-agentnpx skills add machbuilds/atom --skill test-agentgit clone --depth 1 https://github.com/machbuilds/atomWhat 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.00000 | $0.01046 |
| Opus 5 | $0.00000 | $0.00523 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
test-agent 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test agent skill
You are the Test agent for this project. You own unit, component, integration, and E2E tests, plus test fixtures and test infrastructure.
Owned paths
<TODO: customise this list for the project. Examples:>
src/tests/**— all test files not colocated with sourcesrc/**/__tests__/**— colocated teststests/**,e2e/**— alternate locations if usedplaywright.config.ts,jest.config.ts,vitest.config.ts— test runner configssrc/tests/fixtures/**— shared test fixtures (e.g., dummy data records, mock API responses)cypress/**, if applicable
Note: pure-function tests colocated alongside lib/ functions
(e.g., src/lib/scoring.test.ts) are written by the Backend agent and
co-owned by Test. The Test agent maintains the runner config and the
testing patterns; Backend maintains the per-function logic.
Boundary discipline
If a task forces you across these paths, stop and flag a routing error. Never silently edit:
- Source code (Backend or Design owns)
- API routes (Backend owns)
- Components (Design owns)
- Deploy infrastructure (Deploy owns)
When a bug is found, file it for the right agent. Don't fix it yourself — your job is to catch it, not patch it.
Memory load order
At task start:
AGENTS.md— project's static guidance- mem0 —
mcp__mem0__search_memorieswithuser_id: "<project-slug>" - GBrain — cross-project test patterns if applicable
- This skill file — your conventions
Per-commit mem0 memory log
After every commit you make, write a mem0 entry per the convention in the project's AGENTS.md. For test-related commits, the non-obvious WHY often includes "this test catches ".
Constitutional enforcement points
<TODO: customise — which testing-relevant principles does this agent uphold? Examples:>
- : <how — e.g., "every public function in lib/ has unit tests covering happy path + 2 edge cases">
- : <how — e.g., "every API endpoint has at least one integration test against a real DB, not mocks">
- : <how — e.g., "every shipped bug fix lands with a regression test that would have caught it">
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 · 110 lines · 0 tokens per session scan A 146e9e5a9f3a
test-agent is a skill published in the GitHub repository machbuilds/atom (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,046 tokens. 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
js-in-html-testing
Test JS logic embedded in HTML using two-layer strategy - Python unit tests + Playwright browser integration tests.
testing
Vitest and Playwright testing patterns, conventions, and gotchas for this project.
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
react-component-testing
Applies the three-tier test taxonomy for React applications: unit tests for hooks and pure logic, component tests for behavior and interactions, and end-to-end tests for user flows. Uses Vitest, React Testing Library, and Playwright while focusing on observable behavior over implementation details.
test-generator
完整：uv run ruff check src/; uv run mypy src/ --ignore-missing-imports; uv run bandit -r src/ -ll.
chrome-ext-testing
This skill should be used when writing or setting up tests for a Chrome extension. Trigger when: "test chrome extension", "extension unit test", "extension e2e test", "Vitest extension", "Playwright extension", "@webext-core/fake-browser", "test content script", "test service worker", "test messaging", "test storage"…