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.
npx skills add kenshikobayashi/everything-claude-code-for-business --skill feedback-draftgit clone --depth 1 https://github.com/kenshikobayashi/everything-claude-code-for-businessWrote 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.
[](https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/feedback-draft)<a href="https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/feedback-draft"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/feedback-draft/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.
<a href="https://agentmods.dev/skills/kenshikobayashi/everything-claude-code-for-business/feedback-draft"><img src="https://agentmods.dev/badge/skills/kenshikobayashi/everything-claude-code-for-business/feedback-draft.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00014 | $0.00418 |
| Opus 5 | $0.00007 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00084 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
feedback-draft 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 9d 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.
What it actually says
You are executing the /feedback-draft command. Draft feedback for a person.
Input
$ARGUMENTS — Person and situation description, optionally with:
--type [positive|constructive|360]: Feedback type (default: constructive)
Steps
- Understand the situation and what feedback is needed
- Structure using SBI framework:
- Situation: When/where did this happen?
- Behavior: What specifically did they do? (observable, not interpreted)
- Impact: What was the effect? (on you, the team, the project)
- Add a forward-looking element:
- For positive: "I'd love to see more of this because..."
- For constructive: "Going forward, I'd suggest..." or "What would help is..."
- Review for tone — firm but respectful, specific but not personal
Output Format
## Feedback Draft: [Person]
**Type**: [Positive / Constructive / 360]
### Feedback (SBI Format)
**Situation**: [When and where]
**Behavior**: [What they specifically did — observable facts, not interpretations]
**Impact**: [The effect on you, the team, or the outcome]
**Going Forward**: [What you'd like to see / suggestion for improvement]
---
### Delivery Tips
- **Setting**: [1-on-1 / written / real-time]
- **Timing**: [ASAP / next 1-on-1 / end of sprint]
- **Tone**: [Direct but supportive / celebratory / coaching]
Constraints
- Focus on behavior, not character ("You were late to 3 meetings" not "You're unreliable")
- Be specific — vague feedback is useless
- For constructive feedback, always include a forward-looking suggestion
- Draft only — the user delivers the feedback, not Claude
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.
- 9d ago First seen · 53 lines · 14 tokens per session scan A fd33e8054e12
feedback-draft is a skill published in the GitHub repository kenshikobayashi/everything-claude-code-for-business (2 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 418 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…