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 adamfaik/claude-code-pm-starter --skill file-feedbackgit clone --depth 1 https://github.com/adamfaik/claude-code-pm-starterWrote 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/adamfaik/claude-code-pm-starter/file-feedback)<a href="https://agentmods.dev/skills/adamfaik/claude-code-pm-starter/file-feedback"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/file-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/adamfaik/claude-code-pm-starter/file-feedback"><img src="https://agentmods.dev/badge/skills/adamfaik/claude-code-pm-starter/file-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.00063 | $0.00461 |
| Opus 5.5 | $0.00025 | $0.00184 |
| Sonnet 5.5 | $0.00013 | $0.00092 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
file-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 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.
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
File feedback
A correction made in chat is gone when the session ends. This skill files it so every future session already knows.
The router
Ask what the correction was (or take it from the conversation if it just happened), then route it with four questions, in order:
-
Is it a one-off slip? A typo, a misread, a fluke. Let it go; tell the user nothing needs filing.
-
Was the output wrong because a fact was missing or outdated? File the fact. Company, product, or user knowledge goes into the matching
context/file; project knowledge goes into that project'sbrief.md(usually under Decisions made). Quote the exact line you added. -
Was the process wrong? The steps, the format, the quality bar of a recurring piece of work. Edit the matching skill in
.claude/skills/so the fix runs every time. If no skill exists for that work yet and this is at least the second time it repeats, offer to create one from the correction. -
Is it taste? Not wrong, just not how the user likes it. Add an entry to the Corrections log in
context/preferences.mdin this exact shape:**[The rule, one line.]** Why: [what makes this matter to the user] How to apply: [how a future session should act on it, including edge cases]
Rules
- One correction per entry. If the user gives three corrections, route each separately.
- Write the Why by asking the user if it isn't obvious; a rule without a why gets applied blindly and badly.
- Never file the same rule twice. If an entry already covers it, sharpen that entry instead.
- End by quoting exactly what was written and where, so the user can adjust the wording on the spot.
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 · 31 lines · 63 tokens per session scan A fe66c20ef6d3
file-feedback is a skill published in the GitHub repository adamfaik/claude-code-pm-starter (13 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 461 once invoked, about $0.0003 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-31.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…