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 cuellarfr/design-skills --skill design-opsgit clone --depth 1 https://github.com/cuellarfr/design-skillsWrote 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/cuellarfr/design-skills/design-ops)<a href="https://agentmods.dev/skills/cuellarfr/design-skills/design-ops"><img src="https://agentmods.dev/badge/skills/cuellarfr/design-skills/design-ops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cuellarfr/design-skills/design-ops"><img src="https://agentmods.dev/badge/skills/cuellarfr/design-skills/design-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 47 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.04076 |
| Opus 5 | $0.00023 | $0.02038 |
| Sonnet 5 | $0.00009 | $0.00815 |
| Haiku 4.5 | $0.00005 | $0.00408 |
Grade A, and why
design-ops 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 10d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Ops & Handoff
Operational processes that make design teams effective — sprints, handoff, rituals, documentation, and quality assurance.
Design Sprints
A 5-day process for solving big problems and testing ideas before committing engineering resources. Based on Jake Knapp's Sprint methodology developed at Google Ventures.
When to Sprint
| Signal | Sprint Is Right | Sprint Is Wrong |
|---|---|---|
| Problem clarity | Big problem, unclear solution | Solution already known — just build it |
| Stakes | High — wrong direction costs months | Low — easy to course-correct later |
| Team alignment | Disagreement on approach | Team already aligned |
| Time pressure | Need answers this week | Can run a longer discovery process |
| Complexity | Cross-functional problem | Single-discipline task |
The 5-Day Structure
| Day | Focus | Key Activity | Output |
|---|---|---|---|
| Monday | Map | Define the challenge, set a 2-year goal, map the problem space, pick a target | Sprint questions, problem map, target area |
| Tuesday | Sketch | Review existing solutions, each person sketches solutions individually | Solution sketches (one per person) |
| Wednesday | Decide | Present sketches, vote (dot voting + decider picks), create storyboard | Storyboard for prototype |
| Thursday | Prototype | Build a realistic facade — just enough to test | Testable prototype |
| Friday | Test | 5 user interviews, observe together, identify patterns | Go/no-go decision with evidence |
Sprint Team
| Role | Count | Responsibility |
|---|---|---|
| Decider | 1 | Has authority to make final calls. Usually PM or founder |
| Facilitator | 1 | Runs the process, keeps time, manages energy |
| Designer | 1-2 | Leads sketching, builds prototype |
| Engineer | 1-2 | Feasibility gut-checks, helps prototype |
| Domain expert | 1-2 | Customer support, sales, marketing — whoever knows the user |
| Total | 5-7 | More than 7 is counterproductive |
What ships with it
9 files 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.
- examples/design-sprint-walkthrough.md 15 KB
- examples/handoff-walkthrough.md 16 KB
- references/design-qa.md 12 KB
- references/design-sprints.md 13 KB
- references/documentation-standards.md 9.1 KB
- references/handoff-process.md 9.6 KB
- references/team-rituals.md 10 KB
- templates/design-sprint-template.md 5.5 KB
- templates/handoff-checklist-template.md 4.2 KB
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.
- 10d ago First seen · 325 lines · 45 tokens per session scan A 83b95806ea59
design-ops is a skill published in the GitHub repository cuellarfr/design-skills (54 stars, last pushed 18d ago), licensed MIT. It adds 45 tokens to every session and 4,076 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
Accessibility Audit Helper
Reviews UI code and components for WCAG 2.1 accessibility violations and provides specific fixes.
Form UX Optimizer
Reviews web forms for usability issues — field ordering, validation messages, error states, and accessibility.
straightedge
Design execution engine. Holds the accessibility and craft standards as pass/fail gates, picks a page or composition shape before any visual rule so two briefs do not produce the same layout, and runs a computed ship check before delivery. Use this skill for ANY design or build task in any medium: poster, flyer…
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
frontend-slides
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
goose-graphics
Portable visual skill pack for the Agent Skills ecosystem (Claude Code, Claude Desktop, Claude Cowork, Claude Design, Goose, Cursor, Codex). Discovers community-published styles + formats via the gooseworks CLI, runs an extract-style workflow on reference images, and exports rendered PNGs via Playwright.