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 dayvisonassis/sdd-skills --skill pabx-design-systemgit clone --depth 1 https://github.com/dayvisonassis/sdd-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/dayvisonassis/sdd-skills/pabx-design-system)<a href="https://agentmods.dev/skills/dayvisonassis/sdd-skills/pabx-design-system"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/pabx-design-system/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/dayvisonassis/sdd-skills/pabx-design-system"><img src="https://agentmods.dev/badge/skills/dayvisonassis/sdd-skills/pabx-design-system.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.00098 | $0.01104 |
| Opus 5 | $0.00049 | $0.00552 |
| Sonnet 5 | $0.00020 | $0.00221 |
| Haiku 4.5 | $0.00010 | $0.00110 |
Grade A, and why
pabx-design-system 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 12d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PABX Design System
A fonte-da-verdade canônica do design system e das regras de Angular Material do DRCALL PABX vive dentro desta skill, em:
references/angular-material.md
O documento viaja junto com a skill: ao (re)instalar a skill num projeto/branch, a pasta
references/ é copiada junto, então a referência está sempre disponível — sem depender de
nenhum arquivo externo (IDE, .cursor, etc.). Leia e edite direto em references/angular-material.md.
Três armadilhas desta base que já custaram retrabalho
- Classe do design system que colide com o Bootstrap global.
src/_bootstrap-utilities.scssé importado porstyles.scsse define.btn-secondary,.btn-danger,.btn,.close,.dropdown-item,.nav-linke outras com:hover. Sobrescrever uma delas sem declarar o:hoverdeixa o hover nas mãos do Bootstrap — o botão fica ilegível no tema claro. O gatetails/complete-bootstrap-overridereprova. Ver o bloco.btn-secondaryna referência. .btn-primary-green/.btn-secondary/.data-tableNÃO são globais — cada componente redeclara no próprio CSS. Sem isso o botão nasce preto e a tabela sem estilo.--mat-sys-primarynão existe neste app (resolve para vazio). Para link, usar a classe global.link.
Convenções de UX obrigatórias no módulo de tickets
Aprendidas nas F05–F07 e válidas para toda feature nova do módulo (fonte canônica: a seção
"Convenções de UX obrigatórias" em docs/cadastro_ticket/prd_ticket_module.md):
- Card de ajuda (
help_outlinena linha do título → diálogo "Como … funciona") em todo componente com regra não óbvia. Explicar o que o usuário não tem como adivinhar. - Resolver a tarefa no próprio componente: sugestões calculadas do contexto + busca local, em vez de mandar o operador sair da tela e voltar com um identificador. Ação impossível aparece desabilitada com o motivo no tooltip, não falha no clique.
- Consultar sem perder contexto: referência a outra entidade é âncora
routerLink(ganha Ctrl+clique) e tem prévia em diálogo. - Operação em lote reporta o que fez e o que preservou, com o motivo de cada item.
What ships with it
1 file 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.
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.
- 12d ago First seen · 66 lines · 98 tokens per session scan A daded2c2183e
pabx-design-system is a skill published in the GitHub repository dayvisonassis/sdd-skills (1 stars, last pushed 15d ago), licensed MIT. It adds 98 tokens to every session and 1,104 once invoked, about $0.0005 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-31.
Other skills, from other repositories
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".
information-architecture
Design the structure of a website or product including sitemap, navigation, URL structure, content types, taxonomy, and labeling. Use this skill whenever the user asks to plan a sitemap, design navigation, structure URLs, define content types, build taxonomies, design site search, or organize content at the system…
frontend
Builds, styles, and polishes web UI and UX. Use for any frontend, page, component, styling, layout, animation, or visual-quality task, or when asked to make an interface look or feel a certain way.
shiny-bslib-theming
Advanced theming for Shiny apps using bslib and Bootstrap 5. Use when customizing app appearance with bstheme(), Bootswatch themes, custom colors, typography, brand.yml integration, Bootstrap Sass variables, custom Sass/CSS rules, dark mode and color modes, dynamic theme switching, real-time theming, theme inspection…
tastemaker
Generate genuinely beautiful, on-brand UI instead of generic "AI slop" — use whenever the user asks to build, design, style, or improve a UI, landing page, dashboard, app screen, or component, whenever a PRD/spec needs a design pass before implementation, whenever the user pastes reference images/Pinterest/Dribbble…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…