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 MichaelYcJo/SpecSeal --skill testinggit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/testing)<a href="https://agentmods.dev/skills/michaelycjo/specseal/testing"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/testing/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/michaelycjo/specseal/testing"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00047 | $0.00569 |
| Opus 5.5 | $0.00019 | $0.00228 |
| Sonnet 5.5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
testing 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 7d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/specseal:testing, put each test where it can actually fail
Coverage counts what ran, not what was checked, so a suite can be green and prove nothing. Two questions decide the shape: at which level can this break be observed, and would the test fail if the behavior changed.
The pyramid below is general; its middle tier is where projects differ most, so read the examples as one filling. What sits there is whatever this project's parts have to agree on to work: a service's database and request handlers, a client's screens against a fake backend, a CLI's argument parsing through to its exit codes, a library's public surface against a real consumer, a pipeline's stages against fixture data.
Test Pyramid
Unit Tests (the base, and most tests)
- Pure functions, business logic
- Fast, isolated, no external deps
- Mock at boundaries only
Integration Tests (the middle)
- Component interactions: the seams this project actually has
- Real collaborators where the seam is the point (a test database or container, a fake server, a temp filesystem, a simulator)
- Examples by project kind: database queries and request handlers; a screen driven against a stubbed API; argument parsing through to exit codes; a library exercised the way a caller would
E2E Tests (the top, and the fewest tests)
- Critical user flows only
- Login, checkout, core workflows
- Slower, run less frequently
Test Quality Checklist
- Tests have descriptive names (should_X_when_Y)
- Each test checks ONE thing
- Tests are independent (no ordering dependency)
- Tests cover happy path AND edge cases
- Tests cover error paths
- No test logic complexity (no if or loops in tests)
- Assertions are specific (not just "no error")
Rules
- Write failing test BEFORE fixing bugs
- Don't test implementation details, test behavior
- Don't mock what you don't own (wrap it instead)
- Keep tests fast (seconds, not minutes)
- Coverage target: focus on critical paths, not percentages
Output
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.
- 7d ago Changed · +2 tokens per session b47ca062d036
- 2mo ago First seen · 69 lines · 45 tokens per session scan A 4461c6c6f4bd
testing is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 569 once invoked, about $0.0002 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-31.
Other skills, from other repositories
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
crap-analyzer
Use to produce a risk-based refactor + test plan for recently-changed code on a diff/branch/PR by computing CRAP (complexity × untested) on changed methods. Multi-language — TypeScript, JavaScript, Python, Java, Kotlin, Go, Ruby, C#, Rust, PHP — auto-discovers how the repo generates coverage. Triggers …
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.