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 danjdewhurst/story-skills --skill feedback-triagegit clone --depth 1 https://github.com/danjdewhurst/story-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/danjdewhurst/story-skills/feedback-triage)<a href="https://agentmods.dev/skills/danjdewhurst/story-skills/feedback-triage"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/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/danjdewhurst/story-skills/feedback-triage"><img src="https://agentmods.dev/badge/skills/danjdewhurst/story-skills/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.00135 | $0.04075 |
| Opus 5.5 | $0.00054 | $0.01630 |
| Sonnet 5.5 | $0.00027 | $0.00815 |
| Haiku 4.5 | $0.00014 | $0.00407 |
Grade A, and why
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 10d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feedback Triage
Overview
Process alpha/beta reader feedback as a structured, reconcilable workflow:
collect per-reader feedback files, hold all revision until the round is
complete, synthesize convergent/divergent/single-reader findings into a
decision record with a readiness verdict, and hand a concrete revision plan
to the revision-continuity skill.
Prerequisites
A story project with at least one drafted chapter (or a complete draft) that
readers have read. Verify story.md exists in the project root.
When to Use
- Starting a feedback round (recruiting readers, sending chapters out)
- Giving readers a review copy, including the GitHub Pages review-copy workflow and the reader-note issue form (step 1 of the workflow; other skills point here)
- Recording feedback as it arrives
- Synthesizing a completed round into decisions
- NOT for revising the manuscript (use
revision-continuitywith the synthesis's revision plan) - NOT for the agent's own critique of the draft (use
revision-continuityaudits; reader feedback is external input) - NOT for producing simulated persona reads (use
reader-panel; this skill synthesises the round it writes)
Workflow
1. Set up the round
-
Decide the round scope: which chapters readers get (
chapters-readrange) and how many readers (2–4 per round is typical; one reader is a data point, not a round). -
Create the round folder:
feedback/round-{N}/. -
Give readers a review copy they can open without a terminal. Build it from text you can get back, so the round can be rebuilt and old labels mapped later (step 2 of Collect). Save that text first:
- Git project: work from the book's folder, the one that holds
story.md(cdthere first), because-- .below means the current folder. Check that.gitignorelistsdist/(story initwrites one that does; add the line if it is missing), so earlier review copies stay out of the commit. Then rungit status --untracked-files=all -- .and show the user what it lists: the copy is built from the working tree, but a tag points at the last commit, so uncommitted changes would make the two differ. Look through it for private files (a.env, keys or credentials, scanned documents): unless the user says to commit one, add it to.gitignorefirst. Ask before committing and before tagging. With approval, commit the project folder only (skip the commit when the tree is already clean) and tag that commit:
- Git project: work from the book's folder, the one that holds
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago Changed · +13 lines c79fa3959610
- 16d ago Changed · +1 lines 25925958a75f
- 17d ago Changed · +22 lines · +11 tokens per session d04371bfafa0
- 18d ago Changed · +33 lines 854772854cd2
- 25d ago Changed · +36 lines · +7 tokens per session 1821f015c131
- 27d ago Changed · +33 lines bec4c9f619de
- 29d ago Changed · +17 tokens per session 04ffb5da24d2
- 1mo ago Changed · +27 lines · +33 tokens per session efd8a6a2b579
- 1mo ago Changed e67d920d6f23
- 1mo ago First seen · 120 lines · 67 tokens per session scan A ff293dfc5cd8
feedback-triage is a skill published in the GitHub repository danjdewhurst/story-skills (349 stars, last pushed 4d ago), licensed MIT. It adds 135 tokens to every session and 4,075 once invoked, about $0.0005 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-21.
Other skills, from other repositories
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:system-cleanup
The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…