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-feedbacknpx skills add suuus/ape-context --skill context-feedbackgit 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.00017 | $0.01339 |
| Opus 5 | $0.00009 | $0.00669 |
| Sonnet 5 | $0.00003 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
context-feedback 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wrap up the wizard with a setup report, follow-up scheduling, and a final commit offer.
This is the Evidence layer of the ISEE framework — creating observable signals that flow back upstream.
Process
1. Generate setup report
Retrieve data from the session store to populate the report:
SELECT value FROM session_state WHERE key = 'healthcheck_results';
SELECT value FROM session_state WHERE key = 'distilled_intent';
Fall back to conversation context if not available.
Create .github/context-report.md with a summary of everything configured:
# Context Setup Report
> Generated by the Context Setup Wizard on {date}
## MCP Servers Configured
| Server | Covers | Scoping | Status |
|---|---|---|---|
| github-mcp-server | GitHub repos, PRs, issues | Read+Write | ✅ Connected |
| atlassian-jira | Jira projects | Read-only | ✅ Connected |
| workiq | M365 (SharePoint, Outlook) | Read-only | ✅ Connected |
## Documentation Sources
| Category | Platform | Location | Tag |
|---|---|---|---|
| Engineering docs | SharePoint | engineering site | [reference] |
| Security policies | Backstage | service catalog | [constraint] |
| Deployment process | Confluence | ENG space | [process] |
## Distilled Intent & Constraints
### Intent
- {statements from Phase 8}
### Constraints
- {statements from Phase 8}
### Autonomy Boundaries
- {statements from Phase 8}
## Intent Changes
| Date | Trigger | Added | Modified | Removed |
|------|---------|-------|----------|---------|
| {date} | {trigger} | {n} | {n} | {n} |
Details: [.github/intent-changelog.md](intent-changelog.md)
## Healthcheck Results
- {results from Phase 7}
## Files Modified
- `.mcp.json` — MCP server configurations
- `.github/copilot-instructions.md` — enterprise context and instructions
- `.github/context-report.md` — this report
- `.github/intent-changelog.md` — intent change audit trail
1.5. Validate generated artifacts
Before offering to commit, cross-check all generated artifacts for consistency:
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 · 163 lines · 17 tokens per session scan A 1622d1402aff
context-feedback is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 1,339 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…