respond-to-eval

respond-to-eval is a skill for Claude Code from pedrohcgs/claude-code-my-workflow. It costs 111 tokens per session (568 once invoked), scanned A, original, MIT.

A teaching-feedback skill that turns student course evaluations into a documented plan for improving a course.

In plain words
What is it for?
Use it to analyse written and numeric evaluations, identify teaching priorities, and plan concrete syllabus or slide changes.
Why use it?
It separates recurring themes from isolated comments and connects feedback to specific decisions about what to keep, change, investigate, or leave out.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to analyse written and numeric evaluations, identify teaching priorities, and plan concrete syllabus or slide changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pedrohcgs/claude-code-my-workflow/respond-to-eval
About the project

claude-code-my-workflow is a forkable setup for using Claude Code to produce and review academic papers, slides, data analyses, and replication packages. Researchers use its agents, skills, rules, hooks, and quality checks to coordinate these tasks and verify their results. The catalogue entries define the reusable workflow components for Claude Code.

pedrohcgs/claude-code-my-workflow · 1,707 stars · on GitHub · psantanna.com

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.

Any agent
npx skills add pedrohcgs/claude-code-my-workflow --skill respond-to-eval
Clone the repo
git clone --depth 1 https://github.com/pedrohcgs/claude-code-my-workflow

Made for: Claude Code.

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 respond-to-eval

README.md
[![agentmods](https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval/github.svg)](https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval)
Your own site
<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval/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 respond-to-eval

Your own site · 80×15
<a href="https://agentmods.dev/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval"><img src="https://agentmods.dev/badge/skills/pedrohcgs/claude-code-my-workflow/respond-to-eval.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 568 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 117
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 118
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
  • medium Agent Snooping · line 119
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00111 $0.00568
Opus 5.5 $0.00044 $0.00227
Sonnet 5.5 $0.00022 $0.00114
Haiku 4.5 $0.00011 $0.00057

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

Security

Grade A, and why

respond-to-eval 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 6d 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.

.agents/skills/respond-to-eval/SKILL.md · 30 lines

What it actually says

respond-to-eval

This skill's instructions live in .claude/skills/respond-to-eval/SKILL.md. Read that file now and follow it, with the files it points to. Read AGENTS.md first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

  • Arguments. Where it says $ARGUMENTS, use what the user asked for.
  • Claude Code agents. Where a step hands work to an agent in .claude/agents/ (through the Agent or Task tool), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (/commit runs its verifier before it commits). Read the agent's file for what the step checks.
  • Fresh context. If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced not independently verified, and tell the user to repeat that check in Claude Code (/verify-claims for citations) before relying on it.
  • Claude Code settings. allowed-tools, model, effort, argument-hint and disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.
  • Guards. Claude Code's guard hooks do not run for you. Follow the rules in AGENTS.md yourself; the git pre-commit gate and CI still apply to your commits.
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. 6d ago Changed · -98 lines scan C → A e9b1b65452ad
  2. 1mo ago Changed · -1 lines scan A → C 92622383aa2d
  3. 2mo ago First seen · 129 lines · 111 tokens per session scan A 1a7c7fde3241

Subscribe to this mod's changes

respond-to-eval is a skill published in the GitHub repository pedrohcgs/claude-code-my-workflow (1,707 stars, last pushed 6d ago), licensed MIT. It adds 111 tokens to every session and 568 once invoked, about $0.0004 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-08-30.

Related

respond-to-eval compared with skills from other repositories

respond-to-eval next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
respond-to-evalpedrohcgs/claude-code-my-workflowSkill1.7k6d agoMITA111Claude Code
paper-workflowbrycewang-stanford/Paper-WorkFlowSkill5022d agoMITA101Claude Code
r-econometricsbrycewang-stanford/Auto-Empirical-Research-SkillsSkill5.0k4d agononeA20Claude Code, Codex
econ-management-paper-polishlinkingoscar/econ-management-paper-polishSkill525d agoMITA83Codex
econometrics-phd-leveljayjeo/econometrics-phd-level-skillSkill26mo agoMITA201Claude Code, Codex
did-causalxjtulyc/awesome-rosetta-skillsSkill357mo agononeA75Claude Code, Codex
founder-coachalirezarezvani/claude-skillsSkill30kyesterdayMITA41Claude Code