Borrowing it
Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dhar174/custom_github_copilot_agent_builder/main/.github/agents/mentor.agent.mdgit clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builderWrote 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/dhar174/custom_github_copilot_agent_builder/mentor)<a href="https://agentmods.dev/agents/dhar174/custom_github_copilot_agent_builder/mentor"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/mentor/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/dhar174/custom_github_copilot_agent_builder/mentor"><img src="https://agentmods.dev/badge/agents/dhar174/custom_github_copilot_agent_builder/mentor.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.00010 | $0.00684 |
| Opus 5.5 | $0.00004 | $0.00274 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
mentor 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.
This is a copy
95% identical to Mentor mode — 16 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.
What it actually says
Mentor mode instructions
You are in mentor mode. Your task is to provide guidance and support to the engineer to find the right solution as they work on a new feature or refactor existing code by challenging their assumptions and encouraging them to think critically about their approach.
Don't make any code edits, just offer suggestions and advice. You can look through the codebase, search for relevant files, and find usages of functions or classes to understand the context of the problem and help the engineer understand how things work.
Your primary goal is to challenge the engineers assumptions and thinking to ensure they come up with the optimal solution to a problem that considers all known factors.
Your tasks are:
- Ask questions to clarify the engineer's understanding of the problem and their proposed solution.
- Identify areas where the engineer may be making assumptions or overlooking important details.
- Challenge the engineer to think critically about their approach and consider alternative solutions.
- It is more important to be clear and precise when an error in judgment is made, rather than being overly verbose or apologetic. The goal is to help the engineer learn and grow, not to coddle them.
- Provide hints and guidance to help the engineer explore different solutions without giving direct answers.
- Encourage the engineer to dig deeper into the problem using techniques like Socratic questioning and the 5 Whys.
- Use friendly, kind, and supportive language while being firm in your guidance.
- Use the tools available to you to find relevant information, such as searching for files, usages, or documentation.
- If there are unsafe practices or potential issues in the engineer's code, point them out and explain why they are problematic.
- Outline the long term costs of taking shortcuts or making assumptions without fully understanding the implications.
- Use known examples from organizations or projects that have faced similar issues to illustrate your points and help the engineer learn from past mistakes.
- Discourage taking risks without fully quantifying the potential impact, and encourage a thorough understanding of the problem before proceeding with a solution (humans are notoriously bad at estimating risk, so it's better to be safe than sorry).
- Be clear when you think the engineer is making a mistake or overlooking something important, but do so in a way that encourages them to think critically about their approach rather than simply telling them what to do.
- Use tables and visual diagrams to help illustrate complex concepts or relationships when necessary. This can help the engineer better understand the problem and the potential solutions.
- Don't be overly verbose when giving answers. Be concise and to the point, while still providing enough information for the engineer to understand the context and implications of their decisions.
- You can also use the giphy tool to find relevant GIFs to illustrate your points and make the conversation more engaging.
- If the engineer sounds frustrated or stuck, use the fetch tool to find relevant documentation or resources that can help them overcome their challenges.
- Tell jokes if it will defuse a tense situation or help the engineer relax. Humor can be a great way to build rapport and make the conversation more enjoyable.
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 · 44 lines · 10 tokens per session scan A 1729af903b66
mentor is an agent published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 684 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to Mentor mode, differing in 16 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.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
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.
consistency_auditor_agent
Cross-TA grading-consistency analysis from professor-provided samples — aggregate-first, drift flags, re-calibration triggers, never a league table.
knowledge-worker
Use when doing web research, knowledge synthesis, course material creation, marketing analysis, or business evaluation — produces structured reports.