Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jpoutrin/product-forge/plugin install claude-code-devWrote 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/jpoutrin/product-forge/sync-feedback)<a href="https://agentmods.dev/skills/jpoutrin/product-forge/sync-feedback"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/sync-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.
<a href="https://agentmods.dev/skills/jpoutrin/product-forge/sync-feedback"><img src="https://agentmods.dev/badge/skills/jpoutrin/product-forge/sync-feedback.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.00011 | $0.01564 |
| Opus 5.5 | $0.00004 | $0.00626 |
| Sonnet 5.5 | $0.00002 | $0.00313 |
| Haiku 4.5 | $0.00001 | $0.00156 |
Grade B, and why
sync-feedback 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.
find ~/.claude/learnings/projects -name "*.md" -path "*/feedback/*" How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Feedback
Review feedback captured from your Claude Code sessions and sync to Product Forge.
Usage
/sync-feedback # Show status (default)
/sync-feedback --process # Process captured sessions with LLM analysis
/sync-feedback --review # Review pending feedback
/sync-feedback --export # Export to GitHub issues format
Options
| Option | Description |
|---|---|
--status |
Show feedback statistics across all projects |
--process |
Process captured sessions with LLM to extract feedback |
--review |
Interactive review of pending feedback items |
--export |
Export reviewed feedback to GitHub issue format |
Feedback Location
All feedback is stored in ~/.claude/learnings/:
~/.claude/learnings/
├── projects.json # Registry of opted-in projects
├── stats.json # Global statistics
└── projects/
└── {project-slug}/
└── feedback/
├── improvement/
├── skill-idea/
├── command-idea/
├── bug-report/
└── pattern/
Workflow
1. Enable hooks → /enable-feedback-hooks
2. Work normally → Sessions captured on exit (fast, no LLM)
3. Process → /sync-feedback --process (LLM analyzes sessions)
4. Review → /sync-feedback --review
5. Submit → /sync-feedback --export → Create GitHub issue
Execution Instructions
When the user runs this command:
Process Mode (--process)
-
Run the process-sessions script:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/hooks/process-sessions.py --all -
The script will:
- Find all unprocessed sessions in
~/.claude/learnings/sessions/ - For each session, read the transcript and extract user messages
- Call
claude -pto analyze messages for feedback - Save extracted feedback items to appropriate directories
- Mark sessions as processed
- Find all unprocessed sessions in
-
Display results:
Processing sessions... [process-sessions] Processing session abc12345 for project 'product-forge' [process-sessions] Saved: improvement-add-validation.md [process-sessions] Saved: skill-idea-log-checker.md Processed 3 sessions, found 5 feedback items Run /sync-feedback --review to review extracted feedback.
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.
- 1mo ago First seen · 241 lines · 11 tokens per session scan B f869b880ea7a
sync-feedback is a skill published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 11 tokens to every session and 1,564 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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…
remove
Remove a deployed framework or addon from the current workspace.