asking-for-feedback

asking-for-feedback is a skill for Claude Code, Codex from redhuntlabs/wizard. It costs 28 tokens per session (667 once invoked), scanned A, original, MIT.

A guide for writing requests that ask another person for focused, useful feedback on work or behaviour.

In plain words
What is it for?
Use it when asking for feedback on a draft, code, design, plan, interview, talk, proposal, or a specific aspect of your performance.
Why use it?
It reduces vague replies such as “looks good!” by making the topic, work stage, audience, and requested focus clear.

Skill for Claude CodeCodex

Part of the wizard plugin — 37 skills, 6 commands, 1 agent, 1 hook shipped together

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.

agentmods
npx agentmods add skills/redhuntlabs/wizard/asking-for-feedback
Any agent
npx skills add redhuntlabs/wizard --skill asking-for-feedback
Clone the repo
git clone --depth 1 https://github.com/redhuntlabs/wizard

Made for: Claude Code, Codex.

Or install wizard, the plugin that ships this one along with the rest of its 37 skills, 6 commands, 1 agent, 1 hook.

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 asking-for-feedback

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhuntlabs/wizard/asking-for-feedback.svg)](https://agentmods.dev/skills/redhuntlabs/wizard/asking-for-feedback)
Your own site
<a href="https://agentmods.dev/skills/redhuntlabs/wizard/asking-for-feedback"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/asking-for-feedback.svg" alt="Measured on agentmods" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 667 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00028 $0.00667
Opus 5 $0.00014 $0.00333
Sonnet 5 $0.00006 $0.00133
Haiku 4.5 $0.00003 $0.00067

Measured 4d ago against content hash 3fcdb6f129b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

asking-for-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 4d 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.

spells/everyday/asking-for-feedback/SKILL.md · 77 lines

How it starts

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

Asking for Feedback

What this does

Drafts a feedback request that gets you specific, useful responses instead of "looks good!" Names what kind of feedback you want, what stage the work is at, and what kind of feedback you don't want.

When to use

  • Sharing a draft (doc, code, design, plan) for review
  • Asking a manager or peer how you're doing on a specific dimension
  • Requesting feedback on an interview, talk, or proposal

What you bring (Inputs)

  • The work or behavior you're asking about
  • The dimension you most want feedback on
  • The stage of the work (rough sketch / near-final / shipped)
  • The audience (who you're asking; default = the person who will be affected by the work)

What you get (Output)

A short feedback request that the recipient can answer in 5 minutes.

How it works (Steps)

  1. State the work and its stage explicitly: "Here's a rough draft of X — it's about 40% done."
  2. State the one dimension you want feedback on: "I'd specifically like your read on whether the structure works."
  3. Optionally state what you're NOT looking for: "Don't worry about typos or wording yet."
  4. Tell them how much time you're asking for: "Should take 10 minutes."
  5. Tell them when you need it by, and why that date matters.
  6. End with a specific question, not "let me know what you think."

Quality bar

  • Stage is named (rough / near-final / shipped)
  • One dimension is specified (not "general feedback")
  • Time ask is specific (under 30 minutes for a normal request)
  • A specific question is asked, not an open invitation

Variations

  • Manager feedback: ask about a specific situation, not "how am I doing"
  • Peer code review: name the file or area you're least sure about
  • Talk feedback: ask about one specific section ("did the demo land?")
  • Critical feedback (sensitive): explicitly invite disagreement: "Tell me what you'd change, not what you liked."

Example

Input: A draft project plan, near-final, want feedback on whether the milestones are believable.

Read the full file on GitHub · 77 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. 4d ago First seen · 77 lines · 28 tokens per session scan A 3fcdb6f129b3

Subscribe to this mod's changes

asking-for-feedback is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 667 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-31.