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 ne11nn/cantos-plugin --skill redesign-existing-projectsgit clone --depth 1 https://github.com/ne11nn/cantos-pluginWrote 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/ne11nn/cantos-plugin/redesign-existing-projects)<a href="https://agentmods.dev/skills/ne11nn/cantos-plugin/redesign-existing-projects"><img src="https://agentmods.dev/badge/skills/ne11nn/cantos-plugin/redesign-existing-projects.svg" alt="Measured on agentmods" 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.00045 | $0.00873 |
| Opus 5 | $0.00023 | $0.00436 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
redesign-existing-projects 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 7d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Redesign Skill
How This Works
When applied to an existing project, follow this sequence:
- Scan — Read the codebase. Identify the framework, styling method (Tailwind, vanilla CSS, styled-components, etc.), and current design patterns.
- Diagnose — Run through the audit below. List every generic pattern, weak point, and missing state you find.
- Fix — Apply targeted upgrades working with the existing stack. Do not rewrite from scratch. Improve what's there.
Design Audit
Diagnose by running every rule in references/ui-anti-slop.md (§1 Typography → §9 Strategic Omissions) as a checklist against the existing code. For each rule, record whether the current build violates it. The reference is the full audit superset — every generic-AI-pattern, weak-point, and missing-state check formerly listed here lives there now, so new builds and polish passes get the same comprehensive list. List every violation found before moving to Fix.
Upgrade Techniques
When upgrading a project, pull from these high-impact techniques to replace generic patterns:
Typography Upgrades
- Variable font animation. Interpolate weight or width on scroll or hover for text that feels alive.
- Outlined-to-fill transitions. Text starts as a stroke outline and fills with color on scroll entry or interaction.
- Text mask reveals. Large typography acting as a window to video or animated imagery behind it.
Layout Upgrades
- Broken grid / asymmetry. Elements that deliberately ignore column structure — overlapping, bleeding off-screen, or offset with calculated randomness.
- Whitespace maximization. Aggressive use of negative space to force focus on a single element.
- Parallax card stacks. Sections that stick and physically stack over each other during scroll.
- Split-screen scroll. Two halves of the screen sliding in opposite directions.
Motion Upgrades
- Smooth scroll with inertia. Decouple scrolling from browser defaults for a heavier, cinematic feel.
- Staggered entry. Elements cascade in with slight delays, combining Y-axis translation with opacity fade. Never mount everything at once.
- Spring physics. Replace linear easing with spring-based motion for a natural, weighty feel on all interactive elements.
- Scroll-driven reveals. Content entering through expanding masks, wipes, or draw-on SVG paths tied to scroll progress.
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.
- 7d ago First seen · 67 lines · 45 tokens per session scan A 486975ec0c9a
redesign-existing-projects is a skill published in the GitHub repository ne11nn/cantos-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 873 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
oma-design
AI design specialist skill with DESIGN.md management, anti-pattern enforcement, optional Stitch MCP integration, and component library guidance. Covers typography, color systems, motion design (motion/react, GSAP, Three.js), responsive-first layouts, and accessibility (WCAG 2.2).
aesthetic-instrument
A committed aesthetic in the sense of skills/committed-aesthetic/SKILL.md: every rule below is checkable, and every value was read out of the source — packages/board/public/index.html and greatcto-site/styles.css — rather than chosen to write this document.
committed-aesthetic
How to write — and how to use — a skill that IS one aesthetic rather than a catalogue of them. A catalogue lets an agent pick, and it picks the modal option; a committed aesthetic makes it execute one thing precisely, against rules you can check. Use when a design keeps coming out competent and forgettable, when…
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
ux-design
This skill should be used when the user mentions keywords related to ux-design.
frontend-aesthetics
How to make frontends that look genuinely designed instead of generic "AI slop", and how to verify UI work the pipeline can't catch with a test suite. Load whenever a task builds or restyles a user-facing surface — a page, a component, a full redesign, a dashboard, a marketing site. Covers distinctive typography…