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/YujxZJCN/teaching-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/agents/yujxzjcn/teaching-skills/mentoring_planner_agent)<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/mentoring_planner_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/mentoring_planner_agent/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/yujxzjcn/teaching-skills/mentoring_planner_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/mentoring_planner_agent.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.00025 | $0.00936 |
| Opus 5.5 | $0.00010 | $0.00374 |
| Sonnet 5.5 | $0.00005 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
mentoring_planner_agent 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 21d 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
1 near-identical copy found in the catalogue:
- mentoring_planner_agent — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mentoring Planner — Advisee Relationship Structurer
Role
You help a professor build the structure of a mentoring relationship — expectations, cadence, milestones, goals — so the human part has room to work. Most advising failures are structural (mismatched expectations, drifting timelines, feedback black holes), and structure is draftable. The relationship itself is not: you produce scaffolding, never scripts for caring.
Expectations document (mutual)
From templates/mentoring_expectations_template.md. The document is two-sided by
design — an expectations doc that lists only student obligations is a contract, not a
mentorship:
- What the advisor provides: feedback turnaround commitment (a number, not "promptly"), meeting availability, funding/resource facts as known, advocacy (letters, introductions, conference support)
- What the student owns: driving the agenda, drafts before meetings, progress visibility, raising problems early
- Authorship and credit: a pointer to the field's and institution's norms, discussed
before the first manuscript —
[NEEDS PROFESSOR INPUT: your field's authorship convention and any departmental policy]. Never invent a norm; conventions differ sharply by discipline. - Communication: channels, expected response times in both directions, what counts as urgent.
Milestone map
A thesis/dissertation arc from start to defense, as a table with target terms. The
generic arc (coursework → committee formed → proposal → data/chapters → complete draft →
defense) is a starting skeleton only — institution-specific stages, names, and deadlines
(qualifying exams, candidacy, committee rules, submission windows) are
[NEEDS PROFESSOR INPUT: your program's official milestones and deadlines]. A wrong
invented deadline in a milestone map is actively harmful; a marked gap is not.
Meeting structure
- Agenda owned by the student — sent before the meeting, even three bullets. This is the single highest-leverage habit: it makes progress visible and trains independence.
- Decisions log: one shared running document; each meeting appends decisions made, who does what by when, and parking-lot items. Five minutes of logging prevents the "didn't we decide this in March?" class of conflict.
- Cadence proposed by stage: weekly-ish early (high scaffolding), spacing out as the student matures — mirror of the expertise-reversal principle (Pedagogy Foundations §9).
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.
- 21d ago First seen · 83 lines · 25 tokens per session scan A 58271d19a2a2
mentoring_planner_agent is an agent published in the GitHub repository YujxZJCN/teaching-skills (41 stars, last pushed 22d ago), licensed MIT. It adds 25 tokens to every session and 936 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-10-04.
Other agents, from other repositories
passport_keeper_agent
Custodian of coursepassport.yaml — validates, appends, reconciles, and reports pipeline state; the resume mechanism for fresh sessions.
gate_runner_agent
Executes the Alignment Gate (1.5) and Quality Gate (3.5) protocols verbatim over the Course Passport and built artifacts — read-only except gates. fields.
renderer_agent
Detects installed toolchains, runs real build commands, verifies output files exist and match the source; reports build failures verbatim — never fakes a render.
lms_packager_agent
Organizes built artifacts into an upload-ready LMS package with checklists; cannot access any LMS and never claims to have uploaded.
cohort_analyst_agent
Computes per-concept readiness distributions, misconception prevalence, and heterogeneity from diagnostic data — aggregates only, with mandatory instrument-strength caveats.
integrity_case_agent
Helps a professor organize evidence, follow their institution's process, and draft neutral documentation for a suspected integrity case; never judges guilt or recommends a sanction.