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/suuus/ape-context/context-discovernpx skills add suuus/ape-context --skill context-discovergit clone --depth 1 https://github.com/suuus/ape-contextWrote 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/suuus/ape-context/context-discover)<a href="https://agentmods.dev/skills/suuus/ape-context/context-discover"><img src="https://agentmods.dev/badge/skills/suuus/ape-context/context-discover.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 | $0.00030 | $0.01291 |
| Opus 5 | $0.00015 | $0.00646 |
| Sonnet 5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
context-discover 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 4d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Based on the detected stack, find the best MCP servers for each tool category.
FIRST: Check already-installed MCP servers
Before searching for anything, check what's already in .mcp.json. Many tools are already covered:
Known MCP server coverage:
github-mcp-server→ GitHub (issues, PRs, code search, actions, repos) — read + writeworkiq→ Microsoft 365 (SharePoint, Outlook, OneDrive, Teams, Calendar) — read-only (search, query, retrieve). If write access is needed (create pages, send emails, update items), suggest an additional M365/Graph MCP serverplaywright→ Browser automation, testing, screenshots — read + writeatlassian-mcp-server→ Jira, Confluence — read + writedatadog-mcp-server→ Monitoring, logs, metrics — read-onlyazure-mcp-server→ Azure resources, deployments — read + write
When an existing server covers a category in read-only mode, ask the user: "workiq already lets you search SharePoint docs. Do you also need to create/edit content there?" If yes, search for a write-capable MCP server too.
Discovery Chain (for tools NOT already covered)
1. GitHub / Official MCP Catalog
- Search GitHub:
topic:mcp-server+ the vendor/tool name - Check github.com/modelcontextprotocol/servers for official listings
- These get the 🐙 badge
2. Organization Catalog
- Try to read
{org}/.github/mcp-catalog.jsonusingget_file_contents - If it exists, prefer org-approved servers and respect the blocked list
- These get the 🏢 badge
If no org catalog exists, inform the user:
"No org-level MCP catalog was found at
{org}/.github/mcp-catalog.json. An org catalog lets your security team maintain approved/blocked server lists and credential storage policies that apply across all repos. Consider creating one as your MCP adoption grows."
Do not scaffold or create the catalog — just make the recommendation and move on.
3. Vendor Documentation
- Use
web_searchto find: "{tool name} MCP server official" - Use
web_fetchto read install instructions from vendor docs - These get the 🔰 badge
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.
- 4d ago First seen · 127 lines · 30 tokens per session scan A d3918d67f498
context-discover is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 1,291 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…