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/squadcodercom/squadcoder/design-syncnpx skills add squadcodercom/squadcoder --skill design-syncgit clone --depth 1 https://github.com/squadcodercom/squadcoderWhat 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.00134 | $0.01054 |
| Opus 5 | $0.00067 | $0.00527 |
| Sonnet 5 | $0.00027 | $0.00211 |
| Haiku 4.5 | $0.00013 | $0.00105 |
Grade A, and why
sc:design-sync 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Sync — design reference → matching code
Convert a design into code that matches the project's existing system, and keep the two in sync. The goal is parity and consistency: never hard-code a value you could pull from an existing token.
This skill is portable — it relies only on a design reference + the repo, so it works the same in Claude Code, Codex, and opencode/SquadCoder. It does not require any hosted design connector.
Step 0 — identify the design reference
Accept any of:
- Screenshot / image — read it directly (vision); measure spacing/sizes against a known element.
- Figma export — JSON/
design-tokens(W3C tokens), SVG, or a CSS/Tailwind dump. - Design-tokens file —
tokens.json,theme.css, Style Dictionary, etc. - A design URL — if reachable, fetch and read the rendered styles; otherwise ask for an export. If nothing is provided, ask for one — do not invent a design.
Step 1 — read the project's design system FIRST (reuse > duplicate)
Before writing anything, inventory what already exists so you extend it instead of forking it:
- Token sources:
tailwind.config.*, CSS custom properties (--color-*,--space-*),theme.*, anytokens.json, or a design-system package. - Existing components that resemble the target (buttons, cards, inputs) — match their API and styling.
- For SquadCoder/this repo: prefer the shared
@squadcoder/uiprimitives and the bundleddesign-system/israeli-ui-design-systemskills for token architecture and Hebrew typography.
Step 2 — extract design intent, then map to tokens
- Pull the raw values from the reference: palette, type scale, spacing rhythm, radii, shadows, breakpoints, states (hover/active/disabled/focus).
- Map each raw value to the nearest existing token. Only mint a new token when there is a real gap, and add it at the right layer (primitive → semantic → component), never inline.
- Record the mapping (design value → token) so the sync is auditable and repeatable.
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 · 69 lines · 134 tokens per session scan A c69e9a188753
sc:design-sync is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 134 tokens to every session and 1,054 once invoked, about $0.0007 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
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…