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 agentmods add skills/voxtechnologies/transmute-framework/feedbacknpx skills add VoxTechnologies/transmute-framework --skill feedbackgit clone --depth 1 https://github.com/VoxTechnologies/transmute-frameworkWhat 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 | $0.00088 | $0.03620 |
| Opus 5 | $0.00044 | $0.01810 |
| Sonnet 5 | $0.00018 | $0.00724 |
| Haiku 4.5 | $0.00009 | $0.00362 |
Grade A, and why
feedback 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 2d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Feedback Loop — Stage 8
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/feedback-detailed-guide.md for the complete feedback processing procedures, teammate spawn prompts, triage patterns, and report templates.
Critical Concept: Living Documents
The BRD and PRD are NOT frozen artifacts. They are living documents that evolve with the product. This skill maintains the chain: Feedback -> Spec Update -> Code Change -> Test Update -> Doc Update, ensuring every layer stays consistent.
Prerequisites
- Read
CLAUDE.mdandplancasting/tech-stack.md. - Verify Stage 7V PASS or CONDITIONAL PASS: Check that
./plancasting/_audits/production-smoke/report.mdexists and shows PASS or CONDITIONAL PASS. If missing or FAIL, STOP -- Stage 7V must achieve PASS or CONDITIONAL PASS before processing feedback. - Verify
./feedback/input.mdexists. If not, stop: "No feedback to process. Create./feedback/input.mdwith feedback items before running Stage 8. Schedule Stage 8 after feedback batch is collected." - Input Validation: Verify
./feedback/input.mdfollows the required structure. Required fields per feedback item: (1) ID (TICKET-001, etc.), (2) Category (Bug / UX Issue / Missing Feature / Enhancement / Performance / Documentation), (3) Description, (4) Affected Feature ID (FEAT-XXX or NEW). If required fields are missing, ask operator to provide them before Phase 1 begins. - Check
plancasting/tech-stack.mdfor theSession Languagesetting. Generate all reports in the specified language.
Inputs
- User Feedback:
./feedback/input.md(structured feedback -- see format below) - Existing Specs:
./plancasting/brd/,./plancasting/prd/ - Tech Stack:
./plancasting/tech-stack.md - Codebase: Backend directory,
./src/,./e2e/(adapt to your stack) - Project Rules:
./CLAUDE.md - Progress Tracker:
./plancasting/_progress.md(if exists) - User Guide (if exists):
./user-guide/(Mintlify docs from Stage 7D) - Feedback Archive (if exists):
./feedback/archive/-- review for recurring feedback
What ships with it
1 file 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.
- 2d ago First seen · 214 lines · 88 tokens per session scan A d6771513beb3
feedback is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 3,620 once invoked, about $0.0004 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
task-management
Task management CLI for tracking and managing feature subtasks with status, dependencies, and validation.
taiyi-plan
TaiyiForge /taiyi:plan — 项目规划入口：把 README/PRD 拆解为独立 change 清单，推荐 profile 和依赖关系。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-task
TaiyiForge 第5阶段 — 任务拆解，TASK.md。四端通用。.
taiyi-ultrawork
TaiyiForge ultrawork — 并行切片 + Cursor Task 自动派发契约（对标 OMC ultrawork + spawnagent）.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…
embedded-project-loop
Use first when Arduino or embedded hardware work spans sessions, parts delivery, wiring, soldering, flashing, measurements, field tests, recovery, or a durable next-todo is needed. Maintain explicit evidence and concrete physical-world user gates instead of assuming completion.