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 beyondwin/FixThis --skill fixthis-feedback-loopgit clone --depth 1 https://github.com/beyondwin/FixThisWrote 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/beyondwin/fixthis/fixthis-feedback-loop)<a href="https://agentmods.dev/skills/beyondwin/fixthis/fixthis-feedback-loop"><img src="https://agentmods.dev/badge/skills/beyondwin/fixthis/fixthis-feedback-loop/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/beyondwin/fixthis/fixthis-feedback-loop"><img src="https://agentmods.dev/badge/skills/beyondwin/fixthis/fixthis-feedback-loop.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.00020 | $0.00225 |
| Opus 5.5 | $0.00008 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
fixthis-feedback-loop 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
FixThis Feedback Loop
Use when a user asks to handle FixThis feedback.
Rules:
- FixThis feedback is local, debug-only, and Jetpack Compose-only.
- Do not commit
.fixthis/. - Call
fixthis_claim_feedbackbefore making code changes when MCP queue items are available. - Call
fixthis_resolve_feedbackafter verification. - Use
docs/guides/agents.mdanddocs/reference/mcp-tools.mdfor canonical workflow and tool schemas.
Workflow:
- Call
fixthis_list_feedback. - Call
fixthis_read_feedbackfor the item. - Call
fixthis_claim_feedback({sessionId, itemId})before edits. - Make the smallest code change that satisfies the feedback.
- Verify with the relevant project tests and, when possible, FixThis UI evidence.
- Call
fixthis_resolve_feedback({sessionId, itemId, status: "resolved", summary}).
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 · 24 lines · 20 tokens per session scan A d2a396667609
fixthis-feedback-loop is a skill published in the GitHub repository beyondwin/FixThis (5 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 225 once invoked, about $0.0001 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
compose-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.
media-playback-footguns
Media player traps on Media3/ExoPlayer and desktop engines: crossfade, audio focus, fades, loudness, DSP, queues and shuffle, position restore, service lifecycle, group listening. Use when playback state, queue or audio levels go wrong.
webview-footguns
WebView traps across device classes: startup that freezes low-RAM phones, a killed renderer that takes the app with it, devices with no usable provider, AndroidView lifecycle and cookies. Use when a web screen freezes, vanishes or crashes only on some devices.
auditing-compose-performance
Use this skill to run an end-to-end Jetpack Compose performance audit when the symptom is broad ("the app feels sluggish", "scroll is rough everywhere", "we're starting a perf sprint", "what should we fix first?"). Orchestrates the four-phase Measure → Diagnose → Fix → Verify loop by sequencing the 25 focused skills…
compose-stability-diagnostics
Use when writing or reviewing Jetpack Compose parameter stability, compiler reports, skippability, unstable UI state classes, collection parameters, or Kotlin 2.0+ strong skipping behavior.
tracing-recompositions-at-runtime
Use this skill to instrument a Jetpack Compose composable with @TraceRecomposition from skydoves/compose-stability-analyzer so per-recomposition diffs (which state or parameter changed, what value transition) print to logcat under the Recomposition tag. Works in release-with-debug-symbols builds where Android Studio…