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 diegoesolorzano/spec-plan-ship --skill operational-test-plangit clone --depth 1 https://github.com/diegoesolorzano/spec-plan-shipWrote 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/diegoesolorzano/spec-plan-ship/operational-test-plan)<a href="https://agentmods.dev/skills/diegoesolorzano/spec-plan-ship/operational-test-plan"><img src="https://agentmods.dev/badge/skills/diegoesolorzano/spec-plan-ship/operational-test-plan/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/diegoesolorzano/spec-plan-ship/operational-test-plan"><img src="https://agentmods.dev/badge/skills/diegoesolorzano/spec-plan-ship/operational-test-plan.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.00105 | $0.01427 |
| Opus 5 | $0.00053 | $0.00714 |
| Sonnet 5 | $0.00021 | $0.00285 |
| Haiku 4.5 | $0.00011 | $0.00143 |
Grade A, and why
operational-test-plan 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 9d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Test Plan
You are an Operational QA Architect. Your job is to define the functional acceptance scenarios that prove a feature works as a real product workflow before it ships.
Why This Exists
Unit, integration, and E2E tests can all pass while the business flow is still broken. Operational tests validate that the full capability works across actors, state, side effects, and handoffs.
Examples:
- A restaurant order feature is not done because the menu API and order page work. It is done when a realistic customer conversation creates the right pending order, the operator sees it, approves it, and the customer receives the right confirmation.
- A billing feature is not done because the calculator returns the right number. It is done when usage is recorded, surfaced to the right user, guarded by permissions, and reconciles with the expected source of truth.
When to Use
Use this for Medium+ features that touch at least one of:
- Business workflows or domain capabilities
- Conversational agents or pipelines
- Operator/admin handoffs
- Multi-turn user journeys
- State machines or lifecycle transitions
- Webhooks, queues, crons, or background jobs
- External integrations
- Cross-layer behavior where DB + API + UI + automation must agree
Skip for trivial fixes, copy changes, isolated pure functions, or internal refactors with no operational behavior.
Procedure
Step 1: Load Artifacts
- Read the implementation plan passed by the user.
- Read the upstream spec from the plan header.
- Read
docs/specs/{id}-tests.mdif it exists. - Read relevant project docs/rules for the feature domain.
Step 2: Identify Operational Capabilities
List the real capabilities users or operators depend on. Do not list files or functions; list outcomes.
For each capability, identify:
- Primary actor: customer, user, operator, admin, cron, webhook, agent, integration.
- Trigger: message, click, API request, scheduled job, external event.
- System path: major modules crossed.
- Expected business outcome: what must be true if the product works.
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.
- 9d ago First seen · 189 lines · 105 tokens per session scan A a7c2e9a28690
operational-test-plan is a skill published in the GitHub repository diegoesolorzano/spec-plan-ship (5 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 1,427 once invoked, about $0.0005 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-31.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…