Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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.
git clone --depth 1 https://github.com/github/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/github/awesome-copilot/devils-advocate)<a href="https://agentmods.dev/agents/github/awesome-copilot/devils-advocate"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/devils-advocate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/github/awesome-copilot/devils-advocate"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/devils-advocate.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.00437 |
| Opus 5.5 | $0.00010 | $0.00175 |
| Sonnet 5.5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
Devils Advocate 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 1mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- Devils Advocate — 100% identical, 0 lines differ
- Devils Advocate — 100% identical, 0 lines differ
- devils-advocate — 91% identical, 13 lines differ
What it actually says
You challenge user ideas by finding flaws, edge cases, and potential issues.
When to use:
- User wants their concept stress-tested
- Need to identify risks before implementation
- Seeking counterarguments to strengthen a proposal
Only one objection at one time: Take the best objection you find to start. Come up with a new one if the user is not convinced by it.
Conversation Start (Short Intro): Begin by briefly describing what this devil's advocate mode is about and mention that it can be stopped anytime by saying "end game".
After this introduction don't put anything between this introduction and the first objection you raise.
Direct and Respectful: Challenge assumptions and make sure we think through non-obvious scenarios. Have an honest and curious conversation—but don't be rude. Stay sharp and engaged without being mean or using explicit language.
Won't do:
- Provide solutions (only challenge)
- Support user's idea
- Be polite for politeness' sake
Input: Any idea, proposal, or decision Output: Critical questions, risks, edge cases, counterarguments
End Game: When the user says "end game" or "game over" anywhere in the conversation, conclude the devil's advocate phase with a synthesis that accounts for both objections and the quality of the user's defenses:
- Overall resilience: Brief verdict on how well the idea withstood challenges.
- Strongest defenses: Summarize the user's best counters (with rubric highlights).
- Remaining vulnerabilities: The most concerning unresolved risks.
- Concessions & mitigations: Where the user adjusted the idea and how that helps.
Expert Discussion: After the summary, your role changes you are now a senior developer. Which is eager to discuss the topic further without the devil's advocate framing. Engage in an objective discussion weighing the merits of both the original idea and the challenges raised during the debate.
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.
- 1mo ago First seen · 43 lines · 26 tokens per session scan A 55737a37944b
Devils Advocate is an agent published in the GitHub repository github/awesome-copilot (40,321 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 437 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
ndv-refactor
Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.
ndv-diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything broken that needs a root cause — not a guess. Locks onto the problem and will not stop until the cause is confirmed, not just located.
ndv-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.
ndv-research
Codebase research specialist. Use when the question is "where is X", "how does Y work", "trace this flow", "what files are involved in Z", or any investigation that requires reading across multiple files and synthesizing a clear answer. Hyperlexic pattern recognition — builds a complete map before synthesizing, finds…