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 agentmods add skills/promptpartner/agentsmith/new-feedbacknpx skills add PromptPartner/agentsmith --skill new-feedbackgit clone --depth 1 https://github.com/PromptPartner/agentsmithWrote 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/promptpartner/agentsmith/new-feedback)<a href="https://agentmods.dev/skills/promptpartner/agentsmith/new-feedback"><img src="https://agentmods.dev/badge/skills/promptpartner/agentsmith/new-feedback.svg" alt="Measured on agentmods" 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 | $0.00082 | $0.00533 |
| Opus 5 | $0.00041 | $0.00267 |
| Sonnet 5 | $0.00016 | $0.00107 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
new-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.
What it actually says
New feedback note (harness post-incident)
The point is not to fix THIS bug — it's to change the SYSTEM so this whole CLASS is less likely (core/60). Small, specific, traceable to the incident.
When this fires
You were corrected on something a rule could have prevented; you iterated more than you should have; a human stepped in; you re-derived a decision a past session already made. After fixing the immediate thing, capture the lesson.
Fast path — if the Agentsmith CLI is available
Run agentsmith new-feedback "short symptom" — use .agentsmith/agentsmith on macOS/Linux or
.agentsmith\\agentsmith.cmd on Windows when the command is not on PATH. It computes the next number and writes
docs/feedback/NNNN-<slug>.md with the five-stage template, Status open.
Fallback — no CLI
- Next number = (highest existing
docs/feedback/NNNN-*.md+ 1), zero-padded to 4 digits. Numbers are never reused (R9), even if an old entry was archived. - Create
docs/feedback/NNNN-<slug>.md(Status: open) with the five stages:- Evidence / symptom — what was observed, quoted.
- Failure mechanism — WHY the system allowed it (missing rule / vague instruction / absent guardrail / unreached tool / noisy context — almost never "the model was dumb").
- Bounded edit — the smallest change that prevents the whole class.
- Named surface — exactly where it lands (a core rule, a hook, a verify phase, a template); prefer a deterministic surface over prose the model can skip.
- Non-regression — the check that stays red on recurrence. Until it's real, Status stays open.
Report
Name the file, then land the bounded edit on its named surface and flip Status to applied.
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.
- 4d ago First seen · 36 lines · 82 tokens per session scan A 8de3a3e631fa
new-feedback is a skill published in the GitHub repository PromptPartner/agentsmith (185 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 533 once invoked, about $0.0004 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-30.
Other skills, from other repositories
coding-tutor
Personalized coding tutorials that build on your existing knowledge and use your actual codebase for examples. Creates a persistent learning trail that compounds over time using the power of AI, spaced repetition and quizes.
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
oma-explanation
Turn a code change (diff, PR, branch, commit range) into a rich, self-contained interactive HTML explainer with Background / Intuition / Code / Quiz sections. Use for explain, walkthrough, code-change explanation, diff/PR/branch explainer requests — 설명서, 해설, コード解説, 代码讲解. Produces a single offline-capable HTML file…
crit-story
Author a crit story only when the user explicitly invokes /crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
memory-protocol
Universal protocol for total-agent-memory MCP server. Activate at session start, before any non-trivial task, after every significant action, on errors, and at session end. Relevant whenever the user mentions: memory, recall, past context, decisions history, conventions, lessons learned, "продолжаем", "сохранись"…