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/mockupsnpx skills add rakovi4/continue-framework --skill mockupsgit 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.00031 | $0.00674 |
| Opus 5 | $0.00015 | $0.00337 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
mockups 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Interface Mockups
Create production-quality HTML mockups for a user story with mandatory desktop/mobile parity.
Usage
/mockups "Story name"
/mockups 5 # By MVP story number
/mockups # Interactive selection
Phase 1: Context Gathering
Read these files before generating anything:
- Conventions:
ProductSpecification/ui/ui-conventions.md(the single authority for all design rules) - Templates:
ProductSpecification/ui/templates/(browse what's available) ProductSpecification/BriefProductDescription.mdProductSpecification/stories.md(story number lookup)- Story spec:
ProductSpecification/stories/NN-story-name/NN_StoryName.md - Landing page:
Landing/index.html(brand reference) - If exists:
ProductSpecification/stories/NN-story-name/interview.md
Items 5 and 7 resolve stories/ first, then stories/done/ (.claude/rules/workflow.md, "Resolving a story folder") -- a story that later work backports a mockup into has usually closed since. Where the generated files land is Phase 4's template, "Output Location".
Phase 2: Story Selection
Parse user input (by name, by number, or interactive).
Phase 3: Screen Plan (MANDATORY GATE)
You MUST complete this phase fully before writing any HTML file.
- Extract all screen states from the story spec's "Screen States" section. MUST include every state (never skip, merge, or combine).
- Map states to filenames for BOTH desktop AND mobile. Every desktop file MUST have a mobile counterpart.
- Parity check — desktop files = N, mobile files = N. Fix if counts differ.
NEVER proceed to Phase 4 until the Screen Plan table is complete with equal counts.
Phase 4: Generate Mockups
Load .claude/templates/ui/mockup-generation-rules.md for all generation rules, output location, template usage, format, and completion check.
Phase 5: Screenshots
Run /screenshot for both desktop and mobile directories.
Phase 6: Summary
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.
- 3d ago First seen · 72 lines · 31 tokens per session scan A 4bb0cc9e787a
mockups is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 674 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…