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/fulminate-io/knowledge-mcp/test-plannpx skills add fulminate-io/knowledge-mcp --skill test-plangit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/test-plan)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/test-plan"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/test-plan.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.00036 | $0.00629 |
| Opus 5 | $0.00018 | $0.00315 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Test Plan: $ARGUMENTS
For universal orchestration discipline (background spawning, user touch points), reference /orchestrate. This skill is test-planning-specific.
You are creating a structured test plan in the knowledge store. Delegate to the test-planner agent — it researches the codebase, checks existing decisions and rules, then creates a test plan with steps and pass/fail criteria.
Step 0: Check Index Freshness
manage({ "operation": "status" })
If behind HEAD, offer to reindex. Test-planner needs accurate code search.
Step 1: Understand the Goal
Read $ARGUMENTS. If unclear or ambiguous, ask specific clarifying questions before spawning. (Architectural clarification = legitimate touch point.)
Step 2: Spawn the Test-Planner Agent
The test-planner will: search knowledge nodes → batch-search code → check past decisions/rules → deep-dive key functions via traverse → think about trade-offs → discuss scope/ordering/criteria with user → create test plan → verify with assemble.
Step 3: Present the Test Plan
When the test-planner returns:
- Plan structure (steps + ordering)
- Pass/fail criteria per step
- Any assumptions or scope decisions
User reviews before execution (legitimate touch point — plan approval, like /plan reviewer gate).
Step 4: Bridge to Execution
- Ready: suggest
/testto execute. - Needs changes: spawn another test-planner with modifications, or
mutate(operation:"update", ...)directly. - Needs more research: suggest
/researchon the unclear area.
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 · 72 lines · 36 tokens per session scan A 60f0ebb9e8d3
test-plan is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 36 tokens to every session and 629 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…