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 synaptiai/synapti-marketplace --skill feedback-resolutiongit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/feedback-resolution)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/feedback-resolution"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/feedback-resolution/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/synaptiai/synapti-marketplace/feedback-resolution"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/feedback-resolution.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.00103 | $0.01162 |
| Opus 5.5 | $0.00041 | $0.00465 |
| Sonnet 5.5 | $0.00021 | $0.00232 |
| Haiku 4.5 | $0.00010 | $0.00116 |
Grade A, and why
feedback-resolution 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 20d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback Resolution
Contract
Iron law: every change traces to a specific review comment or passes the Boy Scout proximity test; anything else is out-of-context and does not belong in this round. Invoked by /flow:address Phase 1 (collect and categorize feedback) through Phase 4 (verify, post the resolution comment, re-request review). Returns one commit per feedback item (fix(scope): address review — {summary}), separate improve: commits for Boy Scout fixes, a response for every Question or Pushback item, and the resolution comment from templates/resolution-comment.md posted before review is re-requested. Permitted skips: none — pushback replaces a fix only with file:line evidence, a named breaking test, or a quoted CLAUDE.md rule.
Collect
PR_NUM="${PR_NUM:?pass the PR number from the invoking command}"
REPO=$(gh repo view --json nameWithOwner --jq '.nameWithOwner')
gh api repos/$REPO/pulls/$PR_NUM/comments --jq '.[] | {id: .id, path: .path, line: .line, body: .body, author: .user.login}'
gh pr view $PR_NUM --json reviews --jq '.reviews[] | {state: .state, body: .body, author: .author.login}'
Categorize
| Category | Meaning |
|---|---|
| P1 — Must fix | Code bug, security issue, logic error |
| P2 — Should fix | Convention violation, missing test, unclear code |
| P3 — Consider | Style preference, optimization suggestion |
| Question | Needs a response, not necessarily a code change |
| Resolved | Already fixed or no longer relevant |
When the System One decision point address.category is on, /flow:address asks it for each item after the category is chosen; a confident answer can raise the item (P1 > P2 > P3 > Question), never lower it. When address.still_applies is on, an inline comment it finds already addressed is listed as "Already addressed", with the path, lines and commit checked and the confidence, in its reply, the Thread Status table and the summary.
Fix Each Item (one task per item)
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.
- 20d ago Changed · +2 lines e70af4920aa0
- 1mo ago Changed 70270c856933
- 1mo ago Changed · -82 lines 118370d57fcd
- 1mo ago First seen · 143 lines · 103 tokens per session scan A b51457370b86
feedback-resolution is a skill published in the GitHub repository synaptiai/synapti-marketplace (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,162 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
merge-queue
Process the Refinery merge queue - collect agent work, detect and resolve conflicts, merge in dependency order, and verify integration.
document
Run /document pr | changelog | release-note | postmortem (or let it ask) to write the human facing prose about a change. Drafts from the real commits and diff, writing to the right place. Does not write code, tests, or specs.
signing-preflight
Before the first commit of a session, check that commit signing will work — the key is loaded and unlocked — and ask the operator to unlock it once, up front, instead of discovering it after a hundred unsigned commits. Never disables signing silently, never re-signs history without asking. Use at the start of…