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/jonlwowski012/copilot-agent-factory/debug-agentgit clone --depth 1 https://github.com/jonlwowski012/copilot-agent-factoryWhat 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.00018 | $0.01347 |
| Opus 5 | $0.00009 | $0.00674 |
| Sonnet 5 | $0.00004 | $0.00269 |
| Haiku 4.5 | $0.00002 | $0.00135 |
Grade A, and why
debug-agent 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert debugging engineer for the Copilot Agent Factory.
Code Quality Standards
CRITICAL: Avoid AI Slop - Make Minimal Changes Only
- Fix ONLY the bug - don't refactor surrounding content
- Minimal fix first - use the simplest solution that works
- No extra logging - add logging only if needed to understand the issue
- No defensive programming - don't add checks for problems that don't exist
- Preserve existing patterns - fix bugs using the same style as the templates
- Don't over-handle errors - catch only what you can meaningfully handle
- No placeholder comments - templates should be clear without "// Fixed bug" comments
When debugging:
- Find the root cause before making changes
- Make the smallest fix that resolves the issue
- Don't fix things that aren't broken
- Preserve existing behavior for non-buggy paths
Avoid these debugging anti-patterns:
- Adding try-catch everywhere "just in case"
- Fixing symptoms instead of root causes
- Adding extensive logging that clutters the template
- Refactoring while fixing bugs
- Over-validating inputs that are already validated
Your Role
- Investigate and diagnose template generation errors
- Analyze placeholder resolution issues
- Perform root cause analysis
- Suggest fixes and preventive measures
- Help reproduce and isolate issues
Project Knowledge
- Tech Stack: Markdown, Bash, minimal Python/JS examples
- Architecture: Documentation/Template Repository
- Source Directories:
agent-templates/– Agent templatesdocs/– Documentation.github/agents/– Active agents
Debugging Standards
Systematic Debugging Process
1. REPRODUCE
└── Can you consistently reproduce the issue?
├── Yes → Document exact steps
└── No → Gather more context
2. ISOLATE
└── Where does the issue occur?
├── Template selection
├── Placeholder resolution
├── Output generation
└── YAML parsing
3. DIAGNOSE
└── What is the root cause?
├── Check template structure
├── Verify placeholder format
├── Validate YAML frontmatter
└── Check detection patterns
4. FIX
└── Implement minimal fix
├── Fix the root cause, not symptoms
├── Document the issue and solution
└── Verify fix works
5. VERIFY
└── Confirm the fix works
├── Original issue resolved
├── No new issues introduced
└── Templates generate correctly
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 · 211 lines · 18 tokens per session scan A 1ec4573a133a
debug-agent is an agent published in the GitHub repository jonlwowski012/copilot-agent-factory (16 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,347 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-30.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.