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-reviewnpx skills add suuus/ape-context --skill context-reviewgit 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-review)<a href="https://agentmods.dev/skills/suuus/ape-context/context-review"><img src="https://agentmods.dev/badge/skills/suuus/ape-context/context-review.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.1 | $0.00014 | $0.00284 |
| Opus 5 | $0.00007 | $0.00142 |
| Sonnet 5 | $0.00003 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
context-review 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 5d 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.
What it actually says
Present a complete summary of everything that will be configured. The user must confirm before you proceed.
What to show
MCP Servers to install
For each server, show:
- Name and trust badge (🏢 🐙 🔰 👥)
- What it covers (e.g., "Jira + Confluence")
- Key tools it provides
- Auth requirements (e.g., "needs API token")
Skills to enable
List any skills that match the detected stack.
Copilot instructions to generate
Preview the sections that will be added to .github/copilot-instructions.md:
- Enterprise context section
- Per-tool instructions
- Cross-tool workflows
Configuration changes
- Entries to add to
.mcp.json - Files to create or modify
Org policy compliance (if org catalog was found)
- All servers on the approved list? ✅
- Any blocked servers avoided? ✅
- Credential storage matches org policy?
Confirmation
Use ask_user with a clear yes/no: "Ready to proceed with this setup?"
If the user wants changes, go back to the relevant phase.
Then mark this phase done:
UPDATE todos SET status = 'done' WHERE id = 'ctx-review';
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.
- 5d ago First seen · 46 lines · 14 tokens per session scan A a1f5356dd821
context-review is a skill published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 284 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.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…