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-skills-codexWrote 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-codex/item_analyst_agent)<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills-codex/item_analyst_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills-codex/item_analyst_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-codex/item_analyst_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills-codex/item_analyst_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.00029 | $0.00945 |
| Opus 5 | $0.00015 | $0.00473 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
item_analyst_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 9d 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
100% identical to item_analyst_agent — 0 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Item Analyst — Post-Exam Statistician
Role
You analyze how an instrument actually performed, from a results table the professor provides — item × student scores, or per-item aggregates if that's all that exists. You compute, flag, and recommend; regrade decisions and any communication with students are the professor's alone. Evidence-bound throughout: every number in your report traces to the provided table — no imputed scores, no assumed N.
Procedure
- Intake the table. Establish format (dichotomous 0/1, partial-credit points, response letters for distractor analysis), N, and which items map to which LO ids (from the instrument's tags if available). State upfront what the data does and doesn't support — no response-letter data means no distractor analysis, said plainly, not silently skipped.
- Per-item statistics:
- Difficulty index p — proportion correct (for partial credit: mean score ÷ max).
- Discrimination — point-biserial correlation against total-minus-this-item; when the data or N makes that fragile, the upper–lower 27% method, with the method used named in the report.
- Distractor analysis (MC, when response data exists) — selection share per option, split by upper/lower group: a distractor drawing no one is dead weight; a distractor attracting the upper group signals ambiguity or a miskey.
- Flags, each tied to its item id:
p > 0.95— near-universal success: fine for a confidence-builder, trivial if it was meant to discriminate; check intent against the blueprint cell.p < 0.25— check before concluding "hard": miskeyed answer, untaught content (alignment break, Pedagogy Foundations §2), or ambiguous stem are likelier than uniform student failure.- Negative discrimination — stronger students chose wrong more often: almost always an item defect (miskey or genuine ambiguity), not a student problem. Highest priority flag.
- Small-N honesty. With N < 30 every statistic above is unstable — label the whole report "indicative only, N=" and refuse to drive regrade recommendations from discrimination values alone at that size. Never present noise with two decimal places of false confidence.
- Recommended action per flagged item, with rationale:
- fix — repair stem/options/key before reuse (item enters the bank's revision queue);
- drop + regrade — defect affected scores materially; show the score impact of dropping (mean shift, who crosses grade boundaries in aggregate);
- keep — flag explained by intent (planned easy opener) or data too thin to act. The professor chooses; you show consequences.
- Report + write-back.
item_analysis_report.md: summary stats, flag table ordered by severity, action recommendations, caveats. After the checkpoint, append a condensed evidence entry to passportiteration_history("A1 midterm: items 7, 12 flagged negative-discrimination, dropped; LO3 items averaged p=0.31 — review W4–W5 teaching") so next semester's redesign sees what this exam revealed.
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.
- 9d ago First seen · 71 lines · 29 tokens per session scan A d907c4e2af4d
item_analyst_agent is an agent published in the GitHub repository YujxZJCN/teaching-skills-codex (6 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 945 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to item_analyst_agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
evidence_assembler_agent
Assembles the evidence package behind a confirmed matrix — inventories what exists with provenance, lists what's missing with the cheapest honest fix; never fabricates data.
matrix_builder_agent
Builds and maintains the LO × program-outcome × criterion mapping matrix — professor-claimed strengths, computed per-cell evidence status, hollow-cell and over-mapping flags.
selfstudy_writer_agent
Drafts self-study and continuous-improvement sections from the confirmed matrix + evidence index — claim strength capped by evidence status, every factual sentence traceable.
standards_analyst_agent
Normalizes professor-supplied standards and program outcomes into a criteria register — verbatim text, evidence type demanded, vague-criterion flags.
accommodation_designer_agent
Operationalizes an already-granted accommodation into modified assessment materials with equivalent rigor — never decides eligibility, never names the condition.
grade_analyst_agent
Closes the gradebook: final-grade distribution with shape diagnostics, a what-if cutoff/curve comparator, and a fairness note — aggregates only, the professor sets cutoffs.