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/eai-org/agent-toolkit/create-manual-test-instructionsnpx skills add eai-org/agent-toolkit --skill create-manual-test-instructionsgit clone --depth 1 https://github.com/eai-org/agent-toolkitWrote 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/eai-org/agent-toolkit/create-manual-test-instructions)<a href="https://agentmods.dev/skills/eai-org/agent-toolkit/create-manual-test-instructions"><img src="https://agentmods.dev/badge/skills/eai-org/agent-toolkit/create-manual-test-instructions.svg" alt="Measured on agentmods" 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.00030 | $0.00403 |
| Opus 5 | $0.00015 | $0.00201 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
create-manual-test-instructions 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 5d 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
Create manual test instructions
Read the input ticket or requirements document (and, where needed for accurate navigation, the
code it cites). Write the manual-test file in the same directory, naming it by replacing
.REQUIREMENTS or .TICKET with .MANUAL-TEST (e.g. FOO.REQUIREMENTS.md →
FOO.MANUAL-TEST.md); if the input follows neither convention, append .MANUAL-TEST before
.md. If there is no file (pasted text), follow the project's/user's convention for where plans
live (default: .agents/plans/), derive a kebab-case <slug> from the content, and write
<slug>/<slug>.MANUAL-TEST.md there. Running forked, you can't ask mid-run: flag any guessed
location or slug in the final message for the user to verify.
The file must be followable by someone unfamiliar with the ticket — short but complete. Four parts:
- What changed — 1–2 sentences: the feature and the user-visible difference.
- How to get there — concrete navigation to the affected area (entry point, page/screen name, any prerequisite state).
- Before vs after — how the area behaved before, how it should behave now.
- What to verify — checklist of behaviors to confirm, including edge cases (empty values, multiple items, boundaries) where relevant.
Do not modify any source files; the only file you write is the manual-test document.
When done, state the manual-test file's project-relative path.
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.
- 5d ago First seen · 34 lines · 30 tokens per session scan A d5dd40d577b9
create-manual-test-instructions is a skill published in the GitHub repository eai-org/agent-toolkit (43 stars, last pushed 2d ago), licensed MIT. It adds 30 tokens to every session and 403 once invoked, about $0.0002 per session on Opus 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
persona-author
Author or improve an ADD-method persona file (a .add/personas/ slug.md) — the project-fit requirements LENS the ADD engine validates and the design/build/verify/advisor surfaces load. Use when adding a domain expert to the ADD roster, when the add-worker persona mode must DRAFT a persona because none fits the task…
wikispec-wiki
This skills instructs the agent how to maintain the knowledge base in the wiki. Use it when you want to ingest documents or query the wiki.
wikispec-propose
Create specs and designs for a new change. Use this when you need to specify a new change or continue to work on the specification of an existing change.
wikispec-apply
Use the task list for the change to implement the actual change.
wikispec-archive
Drive the agent through the full archive step for a wikispec change. You will use the wikispec tool which is a binary in the path, no need to install anything.
wikispec-plan
Create a tasks list to prepare for the implementation of a change. Use this before implementation to understand what needs to be done.