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 skills add Zfinix/aster --skill write-testsgit clone --depth 1 https://github.com/Zfinix/asterWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zfinix/aster/write-tests)<a href="https://agentmods.dev/skills/zfinix/aster/write-tests"><img src="https://agentmods.dev/badge/skills/zfinix/aster/write-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zfinix/aster/write-tests"><img src="https://agentmods.dev/badge/skills/zfinix/aster/write-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00037 | $0.00311 |
| Opus 5.5 | $0.00015 | $0.00124 |
| Sonnet 5.5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
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 1mo 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
- Copy the house style first. Open the nearest existing test file and match its layout, naming, helpers, and assertion style. A test that looks foreign gets rewritten in review.
- Name tests as behaviors, hierarchically.
timeout_keeps_partial_output,edit_mismatch_embeds_closest_region: the name states the guarantee, and a shared prefix groups the family for filtered runs. - Test the behavior, not the implementation. Assert on outputs and effects, not on private state or call counts. A test that breaks on every refactor protects nothing.
- Every bug fix ships its regression test. Write the test first, watch it fail for the right reason, then fix. A test that never failed proves nothing.
- One behavior per test. Three asserts about one outcome is fine; three scenarios in one test means the name lies about two of them.
- Cover the edge that motivated the code. Empty input, the boundary value, the error path. The happy path usually already works.
- Run the new tests plus the file's old ones, and quote the counts in your report.
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.
- 1mo ago First seen · 26 lines · 37 tokens per session scan A c468d1a516f8
write-tests is a skill published in the GitHub repository Zfinix/aster (129 stars, last pushed 8d ago), licensed Apache-2.0. It adds 37 tokens to every session and 311 once invoked, about $0.0001 per session on Opus 5.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
create-aoh-pack
Use when creating or revising reusable Agentic Ops Harness packs, ops skills, workflows, agent roles, model profiles, runtime requirements, evals, or runtime adapter mappings.
speccrew-test-case-design
Designs structured test cases from Feature Spec and API Contract documents. Focuses on comprehensive test scenario analysis, test case matrix generation, and coverage traceability without involving any code implementation.
speccrew-test-code-gen
Generates executable test code from confirmed test case documents. Reads test case matrix, platform technical conventions, and system design to produce well-structured test files with full traceability to test case IDs.
speccrew-test-manager-orchestration
A test-management workflow that coordinates test design, test-code creation, test execution, and reporting.
speccrew-test-reporter
SpecCrew Test Reporter. Generates comprehensive test reports and individual bug reports from test execution results. Performs root cause analysis and severity classification.
speccrew-test-runner
SpecCrew Test Runner. Executes test code, parses results, and detects deviations between expected and actual outcomes. Reads test code files and system design to run platform-specific test suites.