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/nerds-odd-e/doughnut/manual-testingnpx skills add nerds-odd-e/doughnut --skill manual-testinggit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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 | $0.00037 | $0.00634 |
| Opus 5 | $0.00018 | $0.00317 |
| Sonnet 5 | $0.00007 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
manual-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 3d 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
Purpose: Human-directed or plan-mandated exploratory testing — not a default agent workflow.
Output: Verified behavior report + summary ending with
## MANUAL TEST COMPLETE.
Prerequisites: Assume pnpm sut is already running (backend, frontend,
Mountebank — all auto-reload on code changes). If not running, suggest the user
start it in a separate terminal. To use AI services, set OPENAI_API_TOKEN
before pnpm sut.
Access points:
- Frontend: http://localhost:5173/
- Backend API: http://localhost:9081
Test accounts:
old_learner/passwordanother_old_learner/passwordadmin/password
Linting: The frontend dev server runs linting in the background. Errors appear in terminal output (overlays disabled). Check terminal and fix errors before committing.
<success_criteria>
pnpm sutrunning (or user notified to start it)- Target flows exercised via browser MCP tools
- Results verified with snapshots (and console/network if issues)
- Final output includes
## MANUAL TEST COMPLETE</success_criteria>
## MANUAL TEST COMPLETE
<out_of_scope>
- Do not run proactively without explicit developer or plan request.
- Do not substitute manual testing for automated E2E when the plan calls for Cypress. </out_of_scope>
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.
- 3d ago First seen · 90 lines · 37 tokens per session scan A f5f541453669
manual-testing is a skill published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 3d ago), licensed MIT. It adds 37 tokens to every session and 634 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
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.