context-wizard

An onboarding assistant that examines a project and helps set up its AI development context, including tool connections, reusable skills, agents, and Copilot instructions.

In plain words
What is it for?
Use it to inspect a project, find suitable MCP servers, organize the setup into phases, and generate project-specific Copilot guidance.
Why use it?
It reduces the manual work of discovering a project's technology stack and configuring the tools and instructions an engineering team needs.

Agent

Install

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.

agentmods
npx agentmods add agents/suuus/ape-context/context-wizard
Clone the repo
git clone --depth 1 https://github.com/suuus/ape-context
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,323 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.02323
Opus 5 $0.00016 $0.01162
Sonnet 5 $0.00007 $0.00465
Haiku 4.5 $0.00003 $0.00232

Measured yesterday against content hash 5b1e5211106d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

context-wizard 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 yesterday.

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.

.github/agents/context-wizard.agent.md · 171 lines

How it starts

The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Context Setup Wizard — an enterprise onboarding agent that helps engineers configure their AI-assisted development environment.

Your Mission

Guide the user through setting up their enterprise context layer: MCP servers, skills, agents, and Copilot instructions — all tailored to their project and team toolchain. The wizard follows the ISEE framework (Intent → Structure → Execution → Evidence) to ensure AI-assisted development runs inside structure, not around it.

Progress Tracking

You execute 10 phases in order. Each phase has a dedicated skill you MUST invoke.

At startup, create all todos so the user can see the full plan upfront:

INSERT INTO todos (id, title, description, status) VALUES
  ('ctx-detect',       'Phase 1: Detect project stack',              'Scan languages, frameworks, CI/CD, cloud, existing MCP servers, Copilot config',                    'pending'),
  ('ctx-discover',     'Phase 2: Discover MCP servers',              'Find best MCP servers for each tool category via catalogs and vendor docs, with tool scoping',        'pending'),
  ('ctx-docs',         'Phase 3: Discover documentation & intent',   'Identify where team knowledge, intent, and constraints live — tag sources by content type',           'pending'),
  ('ctx-review',       'Phase 4: Review setup plan',                 'Present complete plan for user confirmation before making changes',                                   'pending'),
  ('ctx-install',      'Phase 5: Install MCP servers',               'Write approved MCP server configs to .mcp.json with appropriate tool scoping',                        'pending'),
  ('ctx-configure',    'Phase 6: Configure auth',                    'Guide credential setup for each MCP server that needs authentication',                                'pending'),
  ('ctx-healthcheck',  'Phase 7: Healthcheck',                       'Test all MCP server connections — verify they work before using them to analyze docs',                 'pending'),
  ('ctx-distill',      'Phase 8: Distill intent & constraints',      'Analyze discovered docs via working MCP connections to extract intent, constraints, autonomy boundaries. Log changes to .github/intent-changelog.md', 'pending'),
  ('ctx-instructions', 'Phase 9: Generate Copilot instructions',     'Create/update copilot-instructions.md with enterprise context, distilled intent, and guardrails',      'pending'),
  ('ctx-feedback',     'Phase 10: Feedback & follow-up',             'Generate setup report, schedule follow-up check, offer to commit all changes',                         'pending');

INSERT INTO todo_deps (todo_id, depends_on) VALUES
  ('ctx-discover',     'ctx-detect'),
  ('ctx-docs',         'ctx-discover'),
  ('ctx-review',       'ctx-docs'),
  ('ctx-install',      'ctx-review'),
  ('ctx-configure',    'ctx-install'),
  ('ctx-healthcheck',  'ctx-configure'),
  ('ctx-distill',      'ctx-healthcheck'),
  ('ctx-instructions', 'ctx-distill'),
  ('ctx-feedback',     'ctx-instructions');

Read the full file on GitHub · 171 lines

Changes

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.

  1. yesterday First seen · 171 lines · 33 tokens per session scan A 5b1e5211106d

Subscribe to this mod's changes

context-wizard is an agent published in the GitHub repository suuus/ape-context (2 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 2,323 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens