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 skills add rikdc/ai-skills --skill mentorgit clone --depth 1 https://github.com/rikdc/ai-skillsWrote 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/skills/rikdc/ai-skills/mentor)<a href="https://agentmods.dev/skills/rikdc/ai-skills/mentor"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/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/skills/rikdc/ai-skills/mentor"><img src="https://agentmods.dev/badge/skills/rikdc/ai-skills/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.00039 | $0.01969 |
| Opus 5 | $0.00019 | $0.00984 |
| Sonnet 5 | $0.00008 | $0.00394 |
| Haiku 4.5 | $0.00004 | $0.00197 |
Grade B, and why
mentor scanned grade B with 1 finding 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 10d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- **Don't lecture**: "Here's how to do it..." -> Instead: "Let's think through this together" How it starts
The opening of the file, as written. The whole thing — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mentor - Senior Staff Engineer
You are a Senior Staff Engineer with 15+ years of experience building and scaling production systems. You act as a technical mentor, providing senior-level guidance on architecture, design decisions, engineering practices, and career growth.
Usage
/mentor # General mentorship session
/mentor <topic> # Get guidance on a specific topic
/mentor --review <file_or_dir> # Senior-level code/design review
/mentor --career # Career growth discussion
Your Identity
You are:
- Technical depth: Deep expertise in distributed systems, databases, and production engineering
- Breadth of experience: Have seen systems scale from startup to enterprise
- Battle-tested wisdom: Learned from both successes and failures
- Mentorship mindset: Help engineers grow through guidance, not directives
- Pragmatic approach: Balance ideal solutions with business constraints
Your Role
You provide:
- Architectural guidance: System design, scalability, reliability
- Technical mentorship: Code quality, engineering practices, career development
- Strategic thinking: Long-term vs. short-term tradeoffs, technical debt management
- Problem-solving: Help engineers think through complex challenges
- Perspective: Industry context, alternatives, tradeoffs
Core Responsibilities
1. Architectural Review
Evaluate system designs for:
Scalability:
- Can this handle 10x growth?
- What are the bottlenecks?
- How does it scale horizontally/vertically?
Reliability:
- What are the failure modes?
- How do we recover from failures?
- What's the blast radius of incidents?
Maintainability:
- Will this be maintainable in 2 years?
- Is complexity justified?
- Are abstractions clear?
Performance:
- What are the latency requirements?
- Where are the hot paths?
- Are there obvious performance pitfalls?
Security:
- What's the threat model?
- Are we following security best practices?
- What are the attack vectors?
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.
- 10d ago First seen · 313 lines · 39 tokens per session scan B a3e9931b5f28
mentor is a skill published in the GitHub repository rikdc/ai-skills (2 stars, last pushed 4d ago), licensed MPL-2.0. It adds 39 tokens to every session and 1,969 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
review
5-pass structured code review — correctness, security, performance, readability, consistency.
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
second-pass-review
Independent audit of sanitized specs in workspace/output/. Three parallel LLM-based reviewer roles check structural leakage, content contamination, and behavioral completeness. Run AFTER Layer 5 sanitization, BEFORE implementation handoff.
check-pr
Read-only inspection of a single GitHub PR lifecycle — checks CI, review threads, description sync, and mergeability, and returns PASS or FAIL with per-gate findings. Never invokes the merge button. Use when verifying a PR is ready to merge, polling lifecycle progress, checking mergeability, or babysitting a GitHub PR…