item_analyst_agent

item_analyst_agent is an agent for Claude Code from YujxZJCN/teaching-skills. It costs 29 tokens per session (945 once invoked), scanned A, original, MIT.

A teaching-analysis skill that examines exam results supplied by a professor to measure question difficulty, how well questions separate stronger and weaker students, and the performance of answer choices.

In plain words
What is it for?
Use it with student-by-question scores or item summaries to analyze difficulty, discrimination, distractors, and possible actions for each question.
Why use it?
It turns a results table into evidence for reviewing questions and planning changes, while avoiding unsupported assumptions about missing data.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the teaching-skills plugin — 5 skills, 30 commands, 22 agents shipped together

Good fit Use it with student-by-question scores or item summaries to analyze difficulty, discrimination, distractors, and possible actions for each question.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yujxzjcn/teaching-skills/item_analyst_agent
Install

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.

Clone the repo
git clone --depth 1 https://github.com/YujxZJCN/teaching-skills

Made for: Claude Code.

Or install teaching-skills, the plugin that ships this one along with the rest of its 5 skills, 30 commands, 22 agents.

Wrote 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.

agentmods badge for item_analyst_agent

README.md
[![agentmods](https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/item_analyst_agent/github.svg)](https://agentmods.dev/agents/yujxzjcn/teaching-skills/item_analyst_agent)
Your own site
<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/item_analyst_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/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.

agentmods 80×15 button for item_analyst_agent

Your own site · 80×15
<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/item_analyst_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/item_analyst_agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 945 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash d907c4e2af4d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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 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.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

assessment-architect/agents/item_analyst_agent.md · 71 lines

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

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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 passport iteration_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.

Read the full file on GitHub · 71 lines

Changes

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.

  1. 10d ago First seen · 71 lines · 29 tokens per session scan A d907c4e2af4d

Subscribe to this mod's changes

item_analyst_agent is an agent published in the GitHub repository YujxZJCN/teaching-skills (26 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.