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 Abilityai/abilities --skill add-testinggit clone --depth 1 https://github.com/Abilityai/abilitiesWrote 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/abilityai/abilities/add-testing)<a href="https://agentmods.dev/skills/abilityai/abilities/add-testing"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/add-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/abilityai/abilities/add-testing"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/add-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.00017 | $0.00557 |
| Opus 5.5 | $0.00007 | $0.00223 |
| Sonnet 5.5 | $0.00003 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
add-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 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
Add Testing Section to Feature Flow
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.add-testing vX.Y — recent: <summary>. Then proceed.
Add a Testing section to a feature flow document using the standard template.
State Dependencies
| Source | Location | Read | Write | Description |
|---|---|---|---|---|
| Feature Flow | docs/memory/feature-flows/{name}.md |
✅ | ✅ | Target document |
Usage
/add-testing {feature-flow-name}
Process
Step 1: Read Feature Flow
Read the feature flow document (docs/memory/feature-flows/{name}.md)
Step 2: Add Testing Section
Add a Testing section before "Related Flows" using the template:
- Prerequisites checklist
- Step-by-step test instructions
- Expected results
- Verification checklist
- Edge cases
- Cleanup steps
- Status tracking
Step 3: Update Document
Use Edit tool to insert the section.
Template
## Testing
**Prerequisites**:
- [ ] [Service/prerequisite 1]
- [ ] [Service/prerequisite 2]
**Test Steps**:
### 1. [Action Name]
**Action**:
- Step 1
- Step 2
**Expected**: What should happen
**Verify**:
- [ ] Check 1
- [ ] Check 2
### 2. [Next Action]
...
**Edge Cases**:
- [ ] Test scenario 1
- [ ] Test scenario 2
**Cleanup**:
- [ ] Cleanup step 1
**Last Tested**: YYYY-MM-DD
**Tested By**: Not yet tested
**Status**: Not Tested
**Issues**: None
Completion Checklist
- Feature flow document read
- Testing section template customized
- Section inserted before "Related Flows"
- Document saved
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 · 99 lines · 17 tokens per session scan A db0c0d8fb1ab
add-testing is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 557 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-09-07.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.