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 YujxZJCN/teaching-skills --skill ta-coordinatorgit 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/skills/yujxzjcn/teaching-skills/ta-coordinator)<a href="https://agentmods.dev/skills/yujxzjcn/teaching-skills/ta-coordinator"><img src="https://agentmods.dev/badge/skills/yujxzjcn/teaching-skills/ta-coordinator/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/yujxzjcn/teaching-skills/ta-coordinator"><img src="https://agentmods.dev/badge/skills/yujxzjcn/teaching-skills/ta-coordinator.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.00156 | $0.01893 |
| Opus 5.5 | $0.00062 | $0.00757 |
| Sonnet 5.5 | $0.00031 | $0.00379 |
| Haiku 4.5 | $0.00016 | $0.00189 |
Grade A, and why
ta-coordinator 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TA Coordinator — Teaching Team Management
Runs the teaching team behind the course: onboarding, grading calibration, workload allocation, weekly meetings, and cross-TA consistency. Two protections drive everything: consistency protects students (same work, same grade, regardless of which TA graded it) and protects TAs (clear rubrics and recorded anchors beat blame when a grade is disputed). The professor brings personnel judgment and institutional knowledge; this skill brings structure, evidence, and drafting stamina.
Prime rule: TAs are apprentice colleagues, not labor to optimize. Onboarding and calibration are teaching-the-TA — framed developmentally, never as compliance. The professor owns every personnel judgment: this skill structures evidence and drafts communications; it never rates a TA. Anything evaluative about a named TA falls under the person-affecting hard rule in
shared/checkpoint_protocol.md— TAs are people too.
Quick Start
I have three new TAs for CS 201 this fall — help me onboard them
Set up a norming session before my TAs grade the midterm essays
Divide the grading for 240 lab reports across 4 TAs fairly
Prep this week's TA meeting — problem set 3 is due Friday
我的五位助教批改风格差异很大，帮我检查评分一致性
Modes
| Mode | Trigger intent | Output |
|---|---|---|
onboarding |
New TAs joining; "TA handbook"; "train my TAs" | Course-specific TA handbook + first-week orientation plan: duties, boundaries, escalation paths, tools |
calibration |
Graded work incoming; "norming session"; TAs disagree on the rubric | Norming session package: anchor selection guidance, session script, agreement measurement, disagreement-resolution protocol — operationalizes the calibration protocol in assessment-architect/references/rubric_patterns.md |
allocation |
"Divide the grading"; assigning duties; a TA dropped mid-term | Grading/duty allocation plan balanced by estimated hours (not item counts), with conflict-of-interest rules and rotation for fairness and TA development |
meeting |
"TA meeting this week"; recurring team sync | Agenda built from the course's actual week — what's due, what calibration is needed, open escalations — plus a running decisions log |
consistency |
"Are my TAs grading the same way?"; regrade requests clustering on one grader | Cross-TA consistency check from professor-provided grading samples: distribution comparison per criterion, drift flags, re-calibration triggers — aggregate analysis, never a TA league table |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 139 lines · 156 tokens per session scan A e81c0093cbe4
ta-coordinator is a skill published in the GitHub repository YujxZJCN/teaching-skills (41 stars, last pushed 22d ago), licensed MIT. It adds 156 tokens to every session and 1,893 once invoked, about $0.0006 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 skills, from other repositories
summarize-activity
Summarize engineering activity in classroomio/classroomio between two dates — merged PRs, still-open PRs opened in that window, and their demo videos — into a markdown report. Use when the user asks what shipped, what happened, or for a summary/recap/digest of engineering work over a date range.
education-expert
Expert-level education technology, learning management systems, and ed-tech platforms. Use when the user mentions edtech, lms, e learning, or assessment, or when the task involves Educational Technology or Standards.
edtech-expert
Expert in education technology, adaptive learning, student analytics, virtual classrooms, assessment tools, and learning management systems. Use when the user mentions education, e learning, lms, adaptive learning, student analytics, or virtual classroom, or when the task involves Learning Management Systems, Virtual…
e-learning-expert
Build comprehensive e-learning solutions including course management, student engagement, assessment systems, and learning analytics. Use when the user mentions an LMS, online courses, SCORM or xAPI, student engagement, assessments and grading, or learning analytics.
criterion-referenced-rubric-generator
Generate a criterion-referenced rubric with descriptive performance levels for a task or objective. Use for marking guides and general curriculum contexts. For Manning programmes where Competent = success, use coherent-rubric-logic-builder instead.
feedback-quality-analyser
Analyse existing written feedback for quality, specificity, actionability, and impact on student learning. Use when reviewing teacher or peer feedback to improve feedback practices.