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-docsnpx skills add suuus/ape-context --skill context-docsgit clone --depth 1 https://github.com/suuus/ape-contextWhat 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.00016 | $0.00692 |
| Opus 5 | $0.00008 | $0.00346 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
context-docs 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 2d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover where team knowledge, intent, and constraints live. This phase identifies documentation sources and tags them by content type — feeding Phase 8 (Distill) where docs are analyzed to extract actionable intent and guardrails.
Use ask_user for each category — one at a time.
Categories
For each, use ask_user with multiple choice + an "Other (specify)" freeform field:
-
Engineering documentation: Where do developers find how-to guides, architecture docs, onboarding?
- Options: Confluence, Notion, GitHub Wiki, repo docs/ folder, SharePoint, Other
-
Security & compliance policies: Where are security standards, compliance requirements, audit docs?
- Options: Dedicated repo, Confluence, SharePoint, Backstage catalog, Other
-
API specifications: Where are API contracts and schemas?
- Options: OpenAPI files in repo, Backstage API catalog, API gateway portal, Confluence, Other
-
Runbooks & incident procedures: Where do engineers find operational runbooks?
- Options: Repo path, Confluence, PagerDuty, Notion, Other
-
Architecture decisions: Where are ADRs and design documents?
- Options: docs/adr/ in repo, Confluence, GitHub Discussions, Other
-
Product documentation: Where to find Product and business related documentation, for example: PRD, BRD, BDD, Product strategy
- Options: Sharepoint/Onedrive, Google Docs, Confluence, repo /docs folder, Other
-
Processes & ceremonies: Where are team workflows, ceremonies, and operational processes documented? (sprint rituals, deployment processes, incident response flows, code review policies, escalation paths)
- Options: Confluence, Notion, GitHub Wiki, repo docs/ folder, SharePoint, Other
For each answer, note:
- The platform (for MCP server matching)
- The specific location (space key, repo path, URL pattern)
- Whether it should be referenced in copilot-instructions.md
- Content tag — classify what kind of content lives there:
[intent]— team priorities, values, strategy, what "done well" looks like[constraint]— security policies, compliance rules, approval requirements, deployment rules[process]— ceremonies, workflows, decision flows, escalation paths[reference]— API specs, onboarding guides, how-to docs
These tags feed Phase 8 (Distill), which uses working MCP connections to analyze the docs and extract actionable intent and constraints.
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.
- 2d ago First seen · 62 lines · 16 tokens per session scan A 176818802338
context-docs is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 692 once invoked, about $0.0001 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…