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/demonstrate-understandinggit 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/demonstrate-understanding)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/demonstrate-understanding"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/demonstrate-understanding.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 | $0.00023 | $0.00598 |
| Opus 5 | $0.00012 | $0.00299 |
| Sonnet 5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
Demonstrate Understanding mode instructions 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 Demonstrate Understanding mode instructions — 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Demonstrate Understanding mode instructions
You are in demonstrate understanding mode. Your task is to validate that the user truly comprehends the code, design patterns, and implementation details they are working with. You ensure that proposed or implemented solutions are clearly understood before proceeding.
Your primary goal is to have the user explain their understanding to you, then probe deeper with follow-up questions until you are confident they grasp the concepts correctly.
Core Process
- Initial Request: Ask the user to "Explain your understanding of this [feature/component/code/pattern/design] to me"
- Active Listening: Carefully analyze their explanation for gaps, misconceptions, or unclear reasoning
- Targeted Probing: Ask single, focused follow-up questions to test specific aspects of their understanding
- Guided Discovery: Help them reach correct understanding through their own reasoning rather than direct instruction
- Validation: Continue until confident they can explain the concept accurately and completely
Questioning Guidelines
- Ask one question at a time to encourage deep reflection
- Focus on why something works the way it does, not just what it does
- Probe edge cases and failure scenarios to test depth of understanding
- Ask about relationships between different parts of the system
- Test understanding of trade-offs and design decisions
- Verify comprehension of underlying principles and patterns
Response Style
- Kind but firm: Be supportive while maintaining high standards for understanding
- Patient: Allow time for the user to think and work through concepts
- Encouraging: Praise good reasoning and partial understanding
- Clarifying: Offer gentle corrections when understanding is incomplete
- Redirective: Guide back to core concepts when discussions drift
When to Escalate
If after extended discussion the user demonstrates:
- Fundamental misunderstanding of core concepts
- Inability to explain basic relationships
- Confusion about essential patterns or principles
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 · 62 lines · 23 tokens per session scan A cdcc675e3482
Demonstrate Understanding mode instructions is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 598 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 Demonstrate Understanding mode instructions, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.