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/redesignnpx skills add VoxTechnologies/transmute-framework --skill redesigngit 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.00099 | $0.03619 |
| Opus 5 | $0.00049 | $0.01809 |
| Sonnet 5 | $0.00020 | $0.00724 |
| Haiku 4.5 | $0.00010 | $0.00362 |
Grade A, and why
redesign 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage 6P-R: Frontend Design Elevation (Interactive Redesign)
Unlike the standard Stage 6P (visual polish — which fixes defects within an existing design system), this stage performs a FULL design elevation: collecting project context interactively, studying reference products, extracting Figma design tokens, making deliberate design decisions with the user, and implementing a cohesive visual overhaul.
Read the detailed guide at ${CLAUDE_SKILL_ROOT}/references/redesign-detailed-guide.md for full phases, anti-slop patterns, component matrices, review procedures, and report templates.
When to Use This vs. Standard 6P
| Scenario | Use |
|---|---|
| App looks functional but needs contrast fixes, hover states, spacing consistency | Standard 6P (polish skill) |
| App looks like generic AI-generated SaaS and needs a distinctive visual identity | This skill (redesign) |
| Rebranding or major design direction change | This skill |
| First-time design system establishment | This skill |
| Post-launch design refresh based on user feedback | This skill |
Pipeline Position
Stage 6P-R occupies the same pipeline slot as 6P (after all Stage 6 quality passes, before Stage 7 deployment). It is an ALTERNATIVE to standard 6P, not an addition. Run one or the other, not both. If 6P has already been run and you want to switch to 6P-R, revert 6P changes first (git revert the 6P commit).
Mutual Exclusion with 6P: 6P and 6P-R are mutually exclusive. To switch from 6P to 6P-R: (1) commit all current work including 6P changes, (2) revert the 6P commit with git revert <6P-commit-hash>, (3) Start a new session and run 6P-R.
Stage Sequence: ... → 6V → [6R — only if 6V found 6V-A/B issues] → 6P-R → 7 (Deploy) → 7V → 7D → 8 / 9
Prerequisites
-
Application must be fully built and functional. Stage 5 complete, Stage 5B audit passed. This stage changes ONLY visual presentation — never functional behavior.
-
Stage 6V/6R should be complete (if applicable):
- If 6R report exists: must show PASS or CONDITIONAL PASS
- If only 6V report exists: must show PASS or CONDITIONAL PASS with only 6V-C issues (6R correctly skipped — 6R cannot fix human-judgment issues)
- If 6V shows CONDITIONAL PASS with 6V-A/6V-B issues: STOP — run 6R first
- If neither exists: verify with operator that prior stages were intentionally skipped
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 · 239 lines · 99 tokens per session scan A 06643d921c84
redesign is a skill published in the GitHub repository VoxTechnologies/transmute-framework (4 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 3,619 once invoked, about $0.0005 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
knowledge-base
Create and maintain a Markdown knowledge base that any AI agent can read, search, and update. Use when the user wants to start a knowledge base, add or update notes, organize docs/notes for an agent or LLM to consume, build an index of notes, or run a cleanup/maintenance pass on an existing MD knowledge base. Triggers…
code-review
Use when code has been written and needs validation before committing, or when the user asks for a code review or security check.
test-generation
Use when the user asks for tests, mentions TDD, or when new code has been written and needs test coverage.
scientific-schematics
Create publication-quality scientific diagrams using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.1 Pro Preview for quality review. Only regenerates if quality is below threshold for your document type. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways…
statistical-power
Sample-size and statistical power calculations for planning studies. Use whenever someone asks "how many subjects/samples/replicates do I need", wants an a priori power analysis, a minimum detectable effect (MDE), a power curve, or needs to justify a sample size for a grant, IRB protocol, or pre-registration. Covers…
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…