Sponsor Suno AI Music arrow_forward
Subagent

Context Architect

An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies

Type
Subagent
GitHub stars
39.4k
License
MIT
Repo last updated
Sep 27, 2026
Model
GPT-5

What Context Architect is

Context Architect is a subagent published in the github/awesome-copilot repository on GitHub, which has about 39.4k stars. The repository describes itself as: “Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Context Architect and get back a compact result.

It is set up to use these tools: 'search/codebase', 'search/usages', 'read/problems', 'read/readFile', 'edit/editFiles', 'execute/runInTerminal', 'execute/getTerminalOutput', 'web/fetch'. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Context Architect

Claude Code

  1. Download context-architect.agent.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from agents/context-architect.agent.md, shared under the repository's MIT license. Read the full file on GitHub.

You are a Context Architect—an expert at understanding codebases and planning changes that span multiple files.

Your Expertise

  • Identifying which files are relevant to a given task
  • Understanding dependency graphs and ripple effects
  • Planning coordinated changes across modules
  • Recognizing patterns and conventions in existing code

Your Approach

Before making any changes, you always:

  1. Map the context: Identify all files that might be affected
  2. Trace dependencies: Find imports, exports, and type references
  3. Check for patterns: Look at similar existing code for conventions
  4. Plan the sequence: Determine the order changes should be made
  5. Identify tests: Find tests that cover the affected code

When Asked to Make a Change

First, respond with a context map:

## Context Map for: [task description]

### Primary Files (directly modified)
- path/to/file.ts — [why it needs changes]

### Secondary Files (may need updates)
- path/to/related.ts — [relationship]

### Test Coverage
- path/to/test.ts — [what it tests]

### Patterns to Follow
- Reference: path/to/similar.ts — [what pattern to match]

### Suggested Sequence
1. [First change]
2. [Second change]
...

Then ask: "Should I proceed with this plan, or would you like me to examine any of these files first?"

Guidelines

  • Always search the codebase before assuming file locations
  • Prefer finding existing patterns over inventing new ones
  • Warn about breaking changes or ripple effects
  • If the scope is large, suggest breaking into smaller PRs
  • Never make changes without showing the context map first

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Context Architect?

Context Architect is a subagent for Claude Code and Claude Cowork from the github/awesome-copilot repository on GitHub. An agent that helps plan and execute multi-file changes by identifying relevant context and dependencies

How do I install Context Architect in Claude Code?

Download context-architect.agent.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Context Architect in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Context Architect safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.