Commonly is a self-hosted collaborative workspace where people work with multiple AI agents, each retaining its own name, memory, skills, and workstation. Teams use it to assign and refine real work across different agent runtimes, and the catalogue entries supply agents, skills, and instructions for use in those rooms.
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 Team-Commonly/commonly --skill commonly-designgit clone --depth 1 https://github.com/Team-Commonly/commonlyWrote 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/team-commonly/commonly/commonly-design)<a href="https://agentmods.dev/skills/team-commonly/commonly/commonly-design"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/commonly-design/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/team-commonly/commonly/commonly-design"><img src="https://agentmods.dev/badge/skills/team-commonly/commonly/commonly-design.svg" alt="Reviewed on agentmods" width="80" 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.00185 | $0.01945 |
| Opus 5.5 | $0.00074 | $0.00778 |
| Sonnet 5.5 | $0.00037 | $0.00389 |
| Haiku 4.5 | $0.00018 | $0.00194 |
Grade A, and why
commonly-design 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 today.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commonly Design
This skill is a thin pointer — the actual design system lives in the commonly repo at frontend/design-system/. Always read those files when invoked, then apply.
Workflow
- Read first — every time this skill triggers:
docs/design/signal-identity.md— the identity as a system (Signal, chosen 2026-09-03): five rules, the complete grey ramp, state grammar, component grammar with exact values, copy rules, the process that made it land, how to add a screen. Read this FIRST for anything visual.frontend/design-system/README.md— voice, content rules, visual fundamentals, iconography, layout, animation; § Identity: Signal is the short form of the doc abovefrontend/design-system/tokens.css— the canonical token set as portable CSSfrontend/src/v2/v2.css(top of file, the.v2-root { ... }block) — the production tokens that ship today
- Match tokens to use case — pick the smallest set of tokens that fit. Don't introduce new colors, sizes, or radii without strong reason; the system is intentionally tight.
- Apply through
var(--v2-*)— never hardcode hex values in v2 components. If a hex appears in a diff, that's almost always a bug. - Cross-check brand voice — read the "Content fundamentals" section in the README. Sentence case, no emoji, em-dashes, agents-by-name.
The two sources of truth and how they relate
| File | What it is | Who reads it |
|---|---|---|
frontend/src/v2/v2.css |
Production tokens — what actually ships, scoped under .v2-root |
The browser |
frontend/design-system/tokens.css |
Same tokens as portable --c-* CSS — for HTML mocks, design-review pages, cross-tool skill use |
Designers, mocks, this skill |
frontend/design-system/README.md |
The system's spec — voice, visual fundamentals, layout (incl. the .v2-root app-shell scroll-containment rule), iconography |
Humans + agents during design work |
frontend/design-system/preview/*.html |
One-card-per-concept review pages — open in a browser to see live samples | Anyone reviewing the system |
frontend/design-system/assets/commonly-mark.svg |
Brand mark — uses currentColor so it inherits the surface |
V2NavRail, marketing, login |
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.
- today First seen · 86 lines · 185 tokens per session scan A d0f98e83cc29
commonly-design is a skill published in the GitHub repository Team-Commonly/commonly (1,370 stars, last pushed today), licensed Apache-2.0. It adds 185 tokens to every session and 1,945 once invoked, about $0.0007 per session on Opus 5.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-10-24.
Other skills, from other repositories
kortix-ui
Build React UI with @kortix/ui, the Kortix component library and the whole Kortix session experience as modules (session workspace, thread, composer, side panel, files, file viewer, terminal, project sidebar and home, customize pages): Kortix Apps, white-label hosts, custom dashboards on @kortix/sdk and apps/web. Load…
make-interfaces-feel-better
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel…
muse
Defining and managing design tokens, applying token systems to existing codebases, building design system foundations. Use for spacing, color, typography, dark mode, cross-platform output.
pixel
Generating pixel-accurate HTML/CSS code from image mockups (PNG/JPG/screenshots) and performing visual verification for faithful reproduction. Use when mockup-to-code generation is needed.
kortix-genui
Renders rich UI in the Kortix web and mobile chat: step rows with photos, option cards, checklists, maps, image galleries, tables, charts, stat rows, comparisons. Load it FIRST, before you answer, when the user asks for: a guide, how-to or first-time process done in the real world (a trip, a flight, a visa, a recipe…
one-design-language
Constrains UI work to the shared design token vocabulary. Use when creating or modifying any component — new CSS values local to one screen are forbidden; every visual decision comes from the existing tokens (spacing, radii, colors, type scale) in globals.css.