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 mikeparcewski/wicked-garden --skill integration-discoverygit clone --depth 1 https://github.com/mikeparcewski/wicked-gardenWrote 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/mikeparcewski/wicked-garden/integration-discovery)<a href="https://agentmods.dev/skills/mikeparcewski/wicked-garden/integration-discovery"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/integration-discovery/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/mikeparcewski/wicked-garden/integration-discovery"><img src="https://agentmods.dev/badge/skills/mikeparcewski/wicked-garden/integration-discovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.01202 |
| Opus 5 | $0.00042 | $0.00601 |
| Sonnet 5 | $0.00017 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
wicked-garden-integration-discovery 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 10d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capability Router
Purpose: Scout available capabilities and decide what to use for a task. Return actionable recommendations so the main agent can execute without discovery overhead.
Why This Matters
Most agents execute with whatever tools are obvious. They don't:
- Check what else is available
- Consider skills that could help
- Look for specialized agents
- Adapt to the user's configured integrations
This skill changes that. It scouts, evaluates, and recommends—so the main agent can focus on execution.
Quick Usage
As Inline Check
Before executing this task, let me check what capabilities could help.
**Task**: Review PR #123 for security issues
**Discovery**:
- MCP: github (PR context), atlassian (link to Jira)
- Skills: qe (test scenarios), platform (security checks)
- Agents: wicked-garden:platform:security-engineer
**Recommendation**: Use security-engineer agent for review, github MCP for PR data.
As Subagent
For complex tasks, spawn integration-discovery as a subagent:
Task tool:
subagent_type: "Explore"
prompt: "Scout available capabilities for: [task description].
Return specific recommendations on which MCP servers,
skills, and agents to use."
The Discovery Process
Step 1: Understand the Task
What does this task need?
- Information sources: Where does data come from?
- Actions: What operations are required?
- Quality concerns: Security, testing, compliance?
- Output: Where do results go?
Step 2: Scout Available Capabilities
Check these sources (see refs/discovery-sources.md for details):
| Source | How to Check | What You Get |
|---|---|---|
| MCP Servers | ListMcpResourcesTool |
External integrations |
| CLI Tools | command -v {tool} |
Installed binaries in PATH |
| Skills | Check Skill tool description | Methodology/expertise |
| Agents | Check Task tool agent list | Specialized workers |
| Built-in Tools | Known set | File ops, search, web |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 169 lines · 84 tokens per session scan A 2e3c78f79197
wicked-garden-integration-discovery is a skill published in the GitHub repository mikeparcewski/wicked-garden (9 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,202 once invoked, about $0.0004 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…