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 bibekpdl/uswds-mcp --skill uswdsgit clone --depth 1 https://github.com/bibekpdl/uswds-mcpWrote 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/bibekpdl/uswds-mcp/uswds)<a href="https://agentmods.dev/skills/bibekpdl/uswds-mcp/uswds"><img src="https://agentmods.dev/badge/skills/bibekpdl/uswds-mcp/uswds/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/bibekpdl/uswds-mcp/uswds"><img src="https://agentmods.dev/badge/skills/bibekpdl/uswds-mcp/uswds.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.00067 | $0.01257 |
| Opus 5.5 | $0.00027 | $0.00503 |
| Sonnet 5.5 | $0.00013 | $0.00251 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
uswds 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 19d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
USWDS
Use this skill when creating, auditing, or converting websites with the U.S. Web Design System. uswds-mcp is an unofficial independent MCP server; do not imply GSA, TTS, or the official USWDS team endorses the output.
Workflow
- Verify the MCP server
io.github.bibekpdl/uswds-mcpis available by callingfind_uswds_classeswith a small query such asusa-button. - Decide structure:
recommend_uswds_structure, and prefer official templates and patterns (get_template,get_pattern) before composing individual components. - Never write
usa-*markup from memory. For every component you use, callget_component_markupand keep its DOM structure, class names, ids and ARIA wiring. Change only text, hrefs and ids that must be unique. Usefind_uswds_classesfor utilities (margin top 2,tablet grid col 6). - For whole pages call
compose_uswds_pagewith real content in explicit sections. Usegenerate_uswds_pageonly as a quick start, and replace every[bracketed]placeholder. - For framework work, call
get_uswds_integration_recipebefore writing code; adapt to React, Next.js, Angular, Rails, Drupal only after preserving the documented DOM shape, classes, ARIA, ids and data attributes. - Run
validate_uswds_markupand fix every error (and explain any remaining warning) before finalizing. Re-run untilpassedis true. Validate project setup withvalidate_uswds_project_setup.
MCP Tools
get_component_markup: official HTML for a component/page template and its variants.compose_uswds_page: complete accessible page from structured sections.find_uswds_classes: real USWDS class names, including utilities.validate_uswds_markup: real-class, structure, forms, ARIA and accessibility validation (fragment or page).generate_uswds_page: quick-start page from free-text requirements.recommend_uswds_structure: USWDS-first site or page structure.search_uswds: search docs, accessibility and usage guidance.get_component/get_pattern/get_template: structured guidance (components include canonical markup).get_uswds_integration_recipe: framework-specific setup for CSS, JavaScript, assets and migration.validate_uswds_project_setup: import path, asset, script, CDN and global CSS risks.
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.
- 19d ago Changed · -1 lines e38cd3bd3132
- 1mo ago First seen · 63 lines · 67 tokens per session scan A 2cc5c6f7e0ce
uswds is a skill published in the GitHub repository bibekpdl/uswds-mcp (2 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,257 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
brand-visual-language
Shape language across type, radius and icons carries brand personality. Use when starting a design system, picking icons or radius tokens, or reviewing visual consistency.
loading-states-and-perceived-performance
Spinners, skeletons and staggered reveals that manage wait times. Use when designing loading states, async data or the feel of a slow interface.
micro-interactions
Small purposeful animations — toggles, animated icons, success moments. Use when designing interactive feedback, success states or loaders.
color-mode-and-theme
Light, dark or both, and when a theme selector is worth it. Use when defining a base palette or deciding on dark mode support.
elevation-and-depth
Shadows and layering that lift elements above the surface. Use when designing cards, dropdowns, modals, tooltips or any floating element.
motion-and-storytelling
Disney's animation principles and cinematic technique applied to UI motion. Use when designing transitions, scroll animations or onboarding motion.