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/rakovi4/continue-framework/align-designnpx skills add rakovi4/continue-framework --skill align-designgit clone --depth 1 https://github.com/rakovi4/continue-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.00049 | $0.00531 |
| Opus 5 | $0.00024 | $0.00266 |
| Sonnet 5 | $0.00010 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade B, and why
align-design scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Locate files**: find mockup in `ProductSpecification/stories/NN-story-name/mockups/desktop/` — or `ProductSpecification/stories/done/NN-story-name/mockups/desktop/` when that story has closed (`.claude/rules/workflo How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/align-design - Align Component to Mockup
Update a frontend component's appearance to match its HTML mockup exactly.
Usage
/align-design "Registration"
/align-design 02 # By story number
/align-design RegistrationPage.tsx # By component file
/align-design # Interactive selection
Workflow
- Load
.claude/tech/{browser-testing}/templates/align-design-checklist.md - Locate files: find mockup in
ProductSpecification/stories/NN-story-name/mockups/desktop/— orProductSpecification/stories/done/NN-story-name/mockups/desktop/when that story has closed (.claude/rules/workflow.md, "Resolving a story folder") — and component infrontend/src/features/ - Extract design tokens: work through every checklist item from the template
- Compare and fix: for each token, compare mockup value vs component value. Fix mismatches using the template's Common Mismatches table and Styling Approach.
- Verify: frontend build command, frontend test command (from
technology.mdConventions), Selenium test if exists, visual check
When dispatched as the staged frontend design-alignment lane, run the entire
workflow plus /design-review, focused frontend coverage, /refactor, and a final
verify-only alignment before returning. Work only inside the coordinator's component
and style manifest. Stage 1 interfaces and other lane manifests are read-only; a
needed conflicting path stops the lane and is reported with evidence. Never stage,
commit, or edit progress.md.
Invoke focused coverage in staged-lane report-only mode. Return reachable gaps to the coordinator without inserting progress steps; the coordinator owns admission and plan mutation after every lane joins.
Key Rules
- NEVER remove
data-testidattributes — Selenium tests depend on them - NEVER change component behavior — only styling
- Match mockup exactly — use mockup's CSS values, not framework defaults (see template for specifics)
- Divider, login link, and other elements outside
<form>in mockup must be outside<form>in component
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 · 47 lines · 49 tokens per session scan B 85be1104bba0
align-design is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 531 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
frontend-design
Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Use whenever the task produces or modifies anything a user will see rendered — websites, landing pages, web apps, dashboards, React/HTML/Vue components, artifacts with visual output, style overhauls, or "make this…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…