Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add buildomator/buildomator/plugin install gsdWrote 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/buildomator/buildomator/add-tests)<a href="https://agentmods.dev/skills/buildomator/buildomator/add-tests"><img src="https://agentmods.dev/badge/skills/buildomator/buildomator/add-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/buildomator/buildomator/add-tests"><img src="https://agentmods.dev/badge/skills/buildomator/buildomator/add-tests.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.00016 | $0.00332 |
| Opus 5.5 | $0.00006 | $0.00133 |
| Sonnet 5.5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
add-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.
This is a copy
86% identical to gsd-add-tests — 36 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
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message test(phase-{N}): add unit and E2E tests from add-tests command
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/add-tests.md </execution_context>
@.planning/STATE.md @.planning/ROADMAP.md
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 · 42 lines · 16 tokens per session scan A 5ba0e8b3f775
add-tests is a skill published in the GitHub repository buildomator/buildomator (98 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 332 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to gsd-add-tests, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
engineering-playbook
A generic senior-engineer operating playbook. MANDATORY for every coding task — plan before you type, test before you claim, debug from evidence, review your own diff.
vibeweaver-core
Compact vibeweaver contract for weak/local models and small tasks. Use on any coding task (implement / modify / debug / deploy); skip for pure Q&A. Load the full contract only when the task needs it: SKILL.md (root) + companions.
vibeweaver-mini
MANDATORY for every coding task: run the checker, fix the first failure, repeat until it prints ALL CHECKS PASS. Do not claim done before that line.
coco-delivery
Implement and verify CoCo features end-to-end (Telegram commands, callbacks, app-server transport, queueing, watchdogs, approvals, and tests). Use when changing this repository's bot behavior and needing repo-specific file targets, workflows, and validation commands. NOT for generic Python tasks outside CoCo.
reqvire-audit
Model quality and diagnostic skill for Reqvire. Use when (1) analyzing model structure, coverage gaps, and improvement recommendations, (2) checking verification coverage and identifying unverified leaf requirements, (3) linting and fixing model quality issues, (4) finding redundant verify relations, or (5) analyzing…
vibeweaver-mini
★ ALWAYS LOAD THIS SKILL BEFORE WRITING ANY CODE. MANDATORY for every coding task: implementing a feature, fixing a bug, writing a function, debugging, writing/running tests, building a frontend, starting a service, scaffolding a project, or modifying any codebase. If the task involves writing or changing code, load…