enable-feedback-hooks

enable-feedback-hooks is a skill for Claude Code from jpoutrin/product-forge. It costs 12 tokens per session (870 once invoked), scanned B, original, MIT.

A command that enables feedback capture for the current project. At the end of a Claude Code session, local analysis looks for improvement ideas and saves them on your machine.

In plain words
What is it for?
Use it to enable or disable project feedback hooks and capture improvement ideas, skill ideas, command ideas, bug reports, or reusable patterns.
Why use it?
It records useful feedback automatically while keeping the captured files local until you choose to synchronize them.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the claude-code-dev plugin — 17 skills, 2 hooks shipped together

Good fit Use it to enable or disable project feedback hooks and capture improvement ideas, skill ideas, command ideas, bug reports, or reusable patterns.

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

Made for: Claude Code.

Or install claude-code-dev, the plugin that ships this one along with the rest of its 17 skills, 2 hooks.

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 enable-feedback-hooks

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/enable-feedback-hooks"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/enable-feedback-hooks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 870 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00012 $0.00870
Opus 5.5 $0.00005 $0.00348
Sonnet 5.5 $0.00002 $0.00174
Haiku 4.5 $0.00001 $0.00087

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

Security

Grade B, and why

enable-feedback-hooks scanned grade B with 1 finding 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 1mo 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .claude/settings.local.json 2>/dev/null || echo '{}'
plugins/claude-code-dev/skills/enable-feedback-hooks/SKILL.md · 138 lines

How it starts

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

Enable Feedback Hooks

Opt-in the current project to capture feedback for Product Forge improvements.

What This Does

When enabled, at the end of each Claude Code session:

  1. Haiku analyzes the conversation for improvement opportunities
  2. Feedback is saved to ~/.claude/learnings/ for later review
  3. No data leaves your machine - feedback stays local until you sync

Feedback Types Captured

  • Improvements - Enhancements to existing skills, commands, or agents
  • Skill ideas - New skills that could help others
  • Command ideas - New commands that could be useful
  • Bug reports - Issues with existing components
  • Patterns - Reusable patterns from your project

Enable for Current Project

Add the Stop hook to .claude/settings.local.json:

/enable-feedback-hooks

Disable

Remove the hook from the current project:

/enable-feedback-hooks --disable

How It Works

Session ends → Haiku analyzes → Saves to ~/.claude/learnings/
                                         ↓
                            Use /sync-feedback to review

Privacy

  • Feedback analysis happens locally via Haiku
  • Feedback files stored only on your machine
  • You review and choose what to submit via /sync-feedback
  • Nothing is sent to Product Forge without your explicit action

Execution Instructions

When the user runs this command:

Enable Mode (default)

  1. Initialize learnings directory if needed:

    ~/.claude/plugins/cache/product-forge-marketplace/scripts/hooks/init-learnings.sh
    
  2. Check if .claude directory exists, create if needed:

    mkdir -p .claude
    
  3. Read existing settings.local.json or create empty structure:

    # If exists, read it
    cat .claude/settings.local.json 2>/dev/null || echo '{}'
    
  4. Add the Stop hook configuration:

    • Merge with existing hooks if any
    • Write the following hook configuration:
    {
      "hooks": {
        "Stop": [
          {
            "hooks": [
              {
                "type": "prompt",
                "prompt": "Analyze this session for Product Forge feedback. Identify:\n1. Improvements to existing skills/commands/agents\n2. New skill/command ideas\n3. Bug reports\n4. Reusable patterns\n\nRespond JSON: {\"feedback\": [{\"type\": \"improvement|skill-idea|command-idea|bug-report|pattern\", \"title\": \"...\", \"description\": \"...\", \"target\": \"plugin/component\"}]} or {\"feedback\": []}",
                "timeout": 60
              },
              {
                "type": "command",
                "command": "python3 ~/.claude/plugins/cache/product-forge-marketplace/scripts/hooks/save-feedback.py",
                "timeout": 10
              }
            ]
          }
        ]
      }
    }
    

Read the full file on GitHub · 138 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. 1mo ago First seen · 138 lines · 12 tokens per session scan B c9f662142274

Subscribe to this mod's changes

enable-feedback-hooks is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 870 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens