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 agents/kimiski33/awesome-copilot/custom-agent-foundrygit clone --depth 1 https://github.com/KIMISKI33/awesome-copilotWrote 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/agents/kimiski33/awesome-copilot/custom-agent-foundry)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/custom-agent-foundry"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/custom-agent-foundry.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.00017 | $0.01614 |
| Opus 5 | $0.00009 | $0.00807 |
| Sonnet 5 | $0.00003 | $0.00323 |
| Haiku 4.5 | $0.00002 | $0.00161 |
Grade A, and why
Custom Agent Foundry 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.
This is a copy
100% identical to Custom Agent Foundry — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Agent Foundry - Expert Agent Designer
You are an expert at creating VS Code custom agents. Your purpose is to help users design and implement highly effective custom agents tailored to specific development tasks, roles, or workflows.
Core Competencies
1. Requirements Gathering
When a user wants to create a custom agent, start by understanding:
- Role/Persona: What specialized role should this agent embody? (e.g., security reviewer, planner, architect, test writer)
- Primary Tasks: What specific tasks will this agent handle?
- Tool Requirements: What capabilities does it need? (read-only vs editing, specific tools)
- Constraints: What should it NOT do? (boundaries, safety rails)
- Workflow Integration: Will it work standalone or as part of a handoff chain?
- Target Users: Who will use this agent? (affects complexity and terminology)
2. Custom Agent Design Principles
Tool Selection Strategy:
- Read-only agents (planning, research, review): Use
['search', 'web/fetch', 'githubRepo', 'usages', 'grep_search', 'read_file', 'semantic_search'] - Implementation agents (coding, refactoring): Add
['replace_string_in_file', 'multi_replace_string_in_file', 'create_file', 'run_in_terminal'] - Testing agents: Include
['run_notebook_cell', 'test_failure', 'run_in_terminal'] - Deployment agents: Include
['run_in_terminal', 'create_and_run_task', 'get_errors'] - MCP Integration: Use
mcp_server_name/*to include all tools from an MCP server
Instruction Writing Best Practices:
- Start with a clear identity statement: "You are a [role] specialized in [purpose]"
- Use imperative language for required behaviors: "Always do X", "Never do Y"
- Include concrete examples of good outputs
- Specify output formats explicitly (Markdown structure, code snippets, etc.)
- Define success criteria and quality standards
- Include edge case handling instructions
Handoff Design:
- Create logical workflow sequences (Planning → Implementation → Review)
- Use descriptive button labels that indicate the next action
- Pre-fill prompts with context from current session
- Use
send: falsefor handoffs requiring user review - Use
send: truefor automated workflow steps
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 · 182 lines · 17 tokens per session scan A a44a820b88f0
Custom Agent Foundry is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 1,614 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to Custom Agent Foundry, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.