interpret-feedback

interpret-feedback is a skill for Claude Code from tobihagemann/turbo. It costs 42 tokens per session (1,029 once invoked), scanned A, original, MIT.

A feedback-interpretation process that examines outside comments in two separate ways and combines the results into clearer explanations of intent, correctness concerns, and unclear points.

In plain words
What is it for?
Use it to understand code-review comments, clarify requested changes, and separate a reviewer's intended fix from uncertain suggestions.
Why use it?
It helps when review comments or other feedback are vague, difficult to interpret, or possibly based on a misunderstanding.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Codex.

Part of the turbo plugin — 71 skills shipped together

Good fit Use it to understand code-review comments, clarify requested changes, and separate a reviewer's intended fix from uncertain suggestions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tobihagemann/turbo/interpret-feedback
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 tobihagemann/turbo --skill interpret-feedback
Clone the repo
git clone --depth 1 https://github.com/tobihagemann/turbo

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 skills.

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 interpret-feedback

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tobihagemann/turbo/interpret-feedback"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/interpret-feedback.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,029 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 pass 7 Sept 2026
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.00042 $0.01029
Opus 5.5 $0.00017 $0.00412
Sonnet 5.5 $0.00008 $0.00206
Haiku 4.5 $0.00004 $0.00103

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

Security

Grade A, and why

interpret-feedback 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 3d 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.

claude/skills/interpret-feedback/SKILL.md · 94 lines

How it starts

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

Interpret Feedback

Run two independent interpretations of third-party feedback in parallel (internal + codex peer), then reconcile into enriched items with clear intent summaries. Designed for feedback where the author's intent is ambiguous or the correctness of suggestions is uncertain.

Step 1: Identify Feedback Items

Determine the feedback to interpret:

  • If feedback items are in conversation context, use them
  • If a file path or URL was provided, read or fetch the content
  • If called by another skill, use the items passed in

For each item, collect whatever context is available: code snippets, diffs, surrounding discussion, file paths, line numbers. More context produces better interpretation.

Step 2: Run Two Interpretations in Parallel

Emit both Agent tool calls below in one assistant message. Each Agent call uses model: "opus" and no name. Wait for every agent to report before continuing. Do not begin the next step on a partial set, and do not relaunch an agent that has not yet reported. That is two Agent tool calls total. Both agents' prompts must direct them to treat the shared working tree and its git index as read-only and to interpret by reading and reasoning. HEAD stays where it is: read other refs with git show <ref>:<path> rather than git checkout or git switch.

Internal Interpretation

Spawn a subagent with the feedback items and all available context. Instruct it to:

  1. Read all referenced code and surrounding context
  2. For each feedback item, produce:
    • Intent: What the feedback author most likely wants changed and why (one to two sentences)
    • Correctness: Whether the suggestion is technically sound — flag concerns if the reviewer may be mistaken, with evidence
    • Ambiguity: Note where the intent is unclear or where multiple valid readings exist
  3. Return structured results per item

Run /peer-review Skill

Launch an Agent tool call whose prompt instructs the subagent to invoke /peer-review via the Skill tool. Describe the request in natural language:

Read the full file on GitHub · 94 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. 3d ago Changed · -22 tokens per session be72452255a7
  2. 2mo ago First seen · 94 lines · 64 tokens per session scan A de2df60779ad

Subscribe to this mod's changes

interpret-feedback is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,029 once invoked, about $0.0002 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

interpret-feedback compared with skills from other repositories

interpret-feedback next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
interpret-feedbacktobihagemann/turboSkill420todayMITA42Claude Code
offensive-c2-frameworksSnailSploit/Claude-RedSkill11kyesterdayMITA250Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-RedSkill11kyesterdayMITA261Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-RedSkill11kyesterdayMITA0Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill11kyesterdayMITA113Claude Code, Codex
fiscalisteromainsimon/paperasseSkill2.6ktodayMITA306Claude Code
comptableromainsimon/paperasseSkill2.6ktodayMITA248Claude Code