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-detectnpx skills add suuus/ape-context --skill context-detectgit 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.00019 | $0.00535 |
| Opus 5 | $0.00010 | $0.00267 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
context-detect 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scan the project in the current working directory and report what you find.
What to scan
- Read current instructions: Analyze the .github/copilot-instructions.md
- Package files: package.json, requirements.txt, go.mod, Cargo.toml, pom.xml, build.gradle
- CI/CD: .github/workflows/, Jenkinsfile, .gitlab-ci.yml, azure-pipelines.yml, .circleci/
- Infrastructure: bicep/terraform/cloudformation files, Dockerfile, docker-compose.yml, kubernetes manifests
- Existing MCP config: Read .mcp.json — list ALL currently configured MCP servers. These are already installed and should be preserved.
- Existing Copilot config: .github/copilot-instructions.md, .github/agents/, .github/skills/, and other relevant files under .github/ , .vscode/
- Git history: check recent commit messages for tool references (JIRA-123, LINEAR-456, ADO-789, etc.)
- Cloud indicators: .azure/, serverless.yml, cdk.json, pulumi files
Critical: existing MCP servers
Read .mcp.json and list every server that's already configured. These are ALREADY WORKING and must be:
- Preserved in all future phases
- Recognized when matching tools to categories (e.g., "workiq" covers M365/SharePoint/Outlook)
- Not duplicated by installing alternatives
What to report
Summarize your findings in a clear list:
- Source control platform
- Languages and frameworks detected
- CI/CD system
- Cloud platform (if any)
- Tool references found in git history
- Already configured MCP servers (from .mcp.json)
- Existing Copilot configuration
- cli tools & scripts that are relevant in this context
Persist results
Write the detected stack to the session store so downstream phases can retrieve it:
INSERT OR REPLACE INTO session_state (key, value)
VALUES ('detected_stack', '{json summary}');
The JSON should include: languages detected, frameworks, CI/CD system, cloud platform, existing MCP servers from .mcp.json, and any tool references found in git history.
Then mark this phase done:
UPDATE todos SET status = 'done' WHERE id = 'ctx-detect';
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 · 54 lines · 19 tokens per session scan A c58526294d69
context-detect is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 535 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…