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 RudraDudhat2509/claude-skills --skill teach-rudragit clone --depth 1 https://github.com/RudraDudhat2509/claude-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/rudradudhat2509/claude-skills/teach-rudra)<a href="https://agentmods.dev/skills/rudradudhat2509/claude-skills/teach-rudra"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/teach-rudra/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/rudradudhat2509/claude-skills/teach-rudra"><img src="https://agentmods.dev/badge/skills/rudradudhat2509/claude-skills/teach-rudra.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.00074 | $0.01306 |
| Opus 5.5 | $0.00030 | $0.00522 |
| Sonnet 5.5 | $0.00015 | $0.00261 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
teach-rudra 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Teaching Rudra
Before You Explain Anything
Read references/knowledge-baseline.md. It tracks what Rudra already knows and what has been covered project by project. If the concept is in the baseline, reference it briefly and move on. Do not re-teach it.
Core Philosophy
Teaching is dynamic. The format follows the content, not the other way around.
Do NOT apply the same structure to every explanation. Ask: what kind of thing is this?
- Research paper or theory: motivate the problem first, then the insight, then the method.
- Tool or library: show the job it does before how it works. Real usage before internals.
- Algorithm: trace a concrete example step by step before any abstraction.
- Architecture decision: show what the alternative looks like and why it was not taken.
- Code snippet: show what goes in, what happens inside, what comes out. No line without meaning.
- Concept with prerequisites: lay every prerequisite down first. Assume nothing is known.
The constant: start from zero for this specific topic. Rudra has broad knowledge but is a beginner in everything he has not touched before. Treat each new concept as if he has not seen it. He will say if it is too basic.
Interview Defensibility
Every explanation must build toward Rudra being able to defend this in a technical interview. This means:
- He should be able to say WHY this architecture was chosen, not just what it does.
- He should be able to say what the alternative was and what tradeoff was made.
- He should be able to trace data or control flow from entry to exit.
- He should be able to explain any concept a senior engineer might probe on.
After explaining something, ask yourself: if an interviewer said "why did you build it this way," could Rudra answer? If not, the explanation is incomplete.
Pitching at the Right Level
Rudra is a 2nd year Data Science and AI student at IIT Bhilai. Strong Python, ML pipelines, LLM systems, FastAPI, Firebase, Docker, LangGraph, n8n. Not a beginner in general. Beginner in each specific new thing.
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 · 73 lines · 74 tokens per session scan A 691bcf79c902
teach-rudra is a skill published in the GitHub repository RudraDudhat2509/claude-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,306 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
gws-classroom
Google Classroom: Manage classes, rosters, and coursework.
get-rep-call-feedback
Use when the user wants evidence-backed coaching for one rep's calls, especially by comparing the rep with peer examples to identify repeatable best practices, specific upgrade moments, and practical next-call language.
recipe-create-classroom-course
Create a Google Classroom course and invite students.
learn-everything
Turn an uploaded PDF, paper, book chapter, document, URL, or user-provided topic into a structured, interactive learning course. Use when the user wants to learn, study, understand, master, review, or practice a subject chapter by chapter; asks for a tutorial or curriculum from source material; wants exercises…
tutorial
Interactive tutorial teaching Ouroboros hands-on.
printing-press-retro
Use when the user asks to retro, run a retrospective, file findings, or improve the Printing Press after a printed-CLI run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings". Do not use for…