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 alyssa-dahlberg/agent-skills --skill tooling-feedback-triagegit clone --depth 1 https://github.com/alyssa-dahlberg/agent-skillsWrote 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/alyssa-dahlberg/agent-skills/tooling-feedback-triage)<a href="https://agentmods.dev/skills/alyssa-dahlberg/agent-skills/tooling-feedback-triage"><img src="https://agentmods.dev/badge/skills/alyssa-dahlberg/agent-skills/tooling-feedback-triage/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/alyssa-dahlberg/agent-skills/tooling-feedback-triage"><img src="https://agentmods.dev/badge/skills/alyssa-dahlberg/agent-skills/tooling-feedback-triage.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.00116 | $0.00895 |
| Opus 5 | $0.00058 | $0.00447 |
| Sonnet 5 | $0.00023 | $0.00179 |
| Haiku 4.5 | $0.00012 | $0.00089 |
Grade A, and why
tooling-feedback-triage 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tooling feedback triage
Acts on the field reports recorded by the tooling-feedback skill. Each report is about an agent, a skill, or a tool that fell short — not just tool usage. That skill only records; this one processes: it gathers the outstanding reports, works out which are real, gets each to a resolution, and clears it away.
What it deliberately does not do is decide the remedy on its own. The right response to a report — edit an agent or skill file, open an issue, adjust config, update docs, or judge it not worth acting on — depends entirely on the project. This skill's job is to surface, validate, and route; the fix comes from the repo's conventions or from the user.
Find the reports
- Default location:
.agent-feedback/, a directory of per-report markdown files (the format tooling-feedback writes). Each has frontmatter (subject— the agent, skill, or tool the report is about — pluskind,date,branch, and an optionalsession) and a body describing what went wrong. - If that directory is absent or empty, check whether the repo keeps feedback elsewhere —
a single tracked file, or a path named in
CLAUDE.md/AGENTS.md/ contributing docs. A quick search for "feedback" across those files usually settles it. - If you still can't find any, say so and stop — there's nothing to triage. Don't manufacture work.
Process each report
For every report found:
- Read it. If it carries a
sessionid and you're on the machine that produced it, you may open that transcript for fuller context; otherwise work from the report alone — it's written to stand without the session. - Validate against the named subject. Open the agent, skill, tool, or config the report names and check the issue is real and still present — not already fixed, not a one-off misread. Reports come from observed failures, so weight them over hypothetical concerns, but confirm before acting.
- Decide the route — using the repo or the user, not your own invention.
- First look for an established convention: does the project document how feedback is resolved (a fix-the-file pattern for the agent/skill, an issue tracker, a changelog)? If so, follow it.
- Absent a convention, present your analysis to the user — the report, whether you think it's valid, and a recommended action — and let them direct. Don't autonomously rewrite tooling or file issues unless the repo's pattern or the user clearly calls for it.
- Carry out the agreed action.
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.
- 11d ago First seen · 64 lines · 116 tokens per session scan A 87d93696d1ce
tooling-feedback-triage is a skill published in the GitHub repository alyssa-dahlberg/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 116 tokens to every session and 895 once invoked, about $0.0006 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.