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 reluctantfuturist/loyal-wingman --skill feedback-processorgit clone --depth 1 https://github.com/reluctantfuturist/loyal-wingmanWrote 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/reluctantfuturist/loyal-wingman/feedback-processor)<a href="https://agentmods.dev/skills/reluctantfuturist/loyal-wingman/feedback-processor"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/feedback-processor/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/reluctantfuturist/loyal-wingman/feedback-processor"><img src="https://agentmods.dev/badge/skills/reluctantfuturist/loyal-wingman/feedback-processor.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.00042 | $0.02260 |
| Opus 5 | $0.00021 | $0.01130 |
| Sonnet 5 | $0.00008 | $0.00452 |
| Haiku 4.5 | $0.00004 | $0.00226 |
Grade A, and why
feedback-processor 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 8d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback Processor Skill
Process alpha reader feedback systematically: extract issues from various formats, prioritize by severity and frequency, track patterns across readers, and maintain structured feedback table for revision planning.
Core Mission
Pattern recognition over single-reader reactions: Don't chase one-off suggestions. Wait for recurring issues across 3+ readers before flagging for revision.
Brutal honesty filter: Distinguish actionable critique from vague praise or random suggestions. Only concrete, specific feedback gets tracked.
Status-driven workflow: Every feedback item has a lifecycle. Track from intake → pattern analysis → triage → action → resolution.
Skill Workflow
1. Intake New Feedback
Triggered by:
- User says "process feedback from [reader name]" or "new feedback in [file/folder]"
- User provides file path to feedback document or screenshot
Input formats supported:
- Markdown files with structured responses
- Screenshot images (WhatsApp, email, Discord, etc.)
- Plain text files
- Audio transcriptions (if provided as text)
Process:
-
Read source material:
Reading feedback from: [file path] Format detected: [markdown/screenshot/text] Reader: [name] Date: [extracted or ask user] -
Extract feedback items:
- Parse structured responses (if using template format)
- OCR/read screenshots for informal feedback
- Identify distinct feedback points
- Separate actionable critique from praise/noise
-
Categorize each item into:
- Character (voice, motivation, consistency, development)
- Plot/Pacing (hook, momentum, structure, clarity)
- World-building (setting, systems, authenticity, info-dumping)
- Prose/Craft (writing quality, dialogue, description)
- Technical (accuracy, research, period details)
- Engagement (interest level, drop-off points, confusion)
- Non-actionable (vague praise, random suggestions)
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.
- 8d ago First seen · 260 lines · 42 tokens per session scan A e40a6dd6e814
feedback-processor is a skill published in the GitHub repository reluctantfuturist/loyal-wingman (7 stars, last pushed 8mo ago), licensed MIT. It adds 42 tokens to every session and 2,260 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…