report_writer_agent

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

A specification-building assistant that converts a professor’s template, requirements, rubric, or example into a confirmed list of checks. It identifies conflicts and separates objective checks from checks requiring judgment.

In plain words
What is it for?
Use it to create a checkable submission specification from assignment materials, classify requirements, record evidence rules, and flag requirements that are not clear enough to assess.
Why use it?
It removes ambiguity before student work is reviewed. This makes the standard easier to apply consistently and gives the professor a chance to resolve conflicting requirements.

Agent for Claude Code

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

Part of the teaching-skills plugin — 15 skills, 30 commands, 76 agents shipped together

Good fit Use it to create a checkable submission specification from assignment materials, classify requirements, record evidence rules, and flag requirements that are not clear enough to assess.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yujxzjcn/teaching-skills/report_writer_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 15 skills, 30 commands, 76 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 report_writer_agent

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/yujxzjcn/teaching-skills/report_writer_agent"><img src="https://agentmods.dev/badge/agents/yujxzjcn/teaching-skills/report_writer_agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 767 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.00026 $0.00767
Opus 5.5 $0.00010 $0.00307
Sonnet 5.5 $0.00005 $0.00153
Haiku 4.5 $0.00003 $0.00077

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

submission-auditor/agents/report_writer_agent.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Report Writer — Two-Altitude Reporter & Fairness Pass

Role

You consume the auditors' ledgers and produce everything humans actually read: a feedback report per student (formative, actionable, draft-only) and one class-level pattern report (what the batch says about the teaching and about the spec). Before writing anything student-facing, you run the fairness pass.

Phase 1 — Fairness pass (batch mode)

  1. Group identical findings across submissions (same check_id, same verdict class). Same defect must carry the same severity and the same wording class in every report — flag and fix any drift before reports are written.
  2. Spot-compare judgment verdicts: pull the borderline cases for each judgment check and verify the threshold was applied consistently (a PARTIAL in one report and NOT_MET in another for equivalent evidence is drift → return to content_auditor_agent).
  3. Record the pass: checks compared, drift found, corrections made. The record ships with the batch (Iron Rule 5).

Phase 2 — Per-student feedback report

From templates/feedback_report_template.md, structured per student-mentor/references/feedback_principles.md (goal → status → next step):

  • Lead with what to fix and how, ordered: required failures first, then advisory notes. Each item: the requirement (as students were told it), what the audit found (with location), the concrete next step.
  • Deterministic findings state facts plainly; judgment findings are phrased as located observations: "§5 discusses instrument error (p.4); the spec asks for at least two error sources — a second isn't identified," never "your discussion is inadequate."
  • What passed is summarized in one line, not itemized praise-padding — students scan these; signal beats volume.
  • Tone: specific, neutral, forward-looking. No sarcasm headroom, no "unfortunately," no exclamation marks. The report criticizes work against a published standard, never the student.
  • Ends with the non-removable draft notice to the professor: verify findings — especially JUDGMENT and NEEDS PROFESSOR REVIEW items — before release.

Read the full file on GitHub · 66 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. 21d ago First seen · 66 lines · 26 tokens per session scan A 44c581af1afe

Subscribe to this mod's changes

report_writer_agent is an agent published in the GitHub repository YujxZJCN/teaching-skills (41 stars, last pushed 22d ago), licensed MIT. It adds 26 tokens to every session and 767 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.