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 blencorp/skills --skill gsa-usdsgit clone --depth 1 https://github.com/blencorp/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/blencorp/skills/gsa-usds)<a href="https://agentmods.dev/skills/blencorp/skills/gsa-usds"><img src="https://agentmods.dev/badge/skills/blencorp/skills/gsa-usds/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/blencorp/skills/gsa-usds"><img src="https://agentmods.dev/badge/skills/blencorp/skills/gsa-usds.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.00077 | $0.00466 |
| Opus 5 | $0.00039 | $0.00233 |
| Sonnet 5 | $0.00015 | $0.00093 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
gsa-usds 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 9d 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.
This is a copy
89% identical to cdc-dibbs-design-system — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
GSA TTS A U.S. Design System
Before editing
- Confirm the product is inside this system's scope.
- Read references/implementation.md before installing, copying, or changing upstream assets.
- Read references/sources.md for provenance, version, and license.
- Inspect and preserve the target project's framework, package manager, asset pipeline, and accessibility tests.
Workflow
- Choose one documented delivery path and pin an exact package, commit, release, or downloaded asset snapshot.
- Use only official components, tokens, templates, and examples that are actually public.
- Extend through documented mechanisms. Label every unsupported addition as custom.
- Record the upstream version or commit and the accepted maturity/maintenance risk.
- Test keyboard operation, focus, names/roles/states, errors, status messages, contrast, zoom/reflow, responsive behavior, and supported browsers.
Boundaries
- Scope: Dense operational federal applications. Do not confuse this React system, named USDS, with the government-wide U.S. Web Design System (USWDS).
- Delivery: React and TypeScript components installed directly from the official Git repository.
- Release: Installed from the official GitHub repository; no npm package is published. Pin an exact commit or tag.
- Do not invent a registry package, public repository, component API, or release commitment.
- Do not imply that a beta, hosted asset, code example, or product-specific repository is government-wide.
- Do not claim legal or WCAG conformance for the completed service solely from component use.
- If this system does not fit the product's requirements, route to the governing system or stop and explain the gap.
References
What ships with it
3 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.
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.
- 9d ago First seen · 37 lines · 77 tokens per session scan A 07fe85bfdc69
gsa-usds is a skill published in the GitHub repository blencorp/skills (5 stars, last pushed 21d ago), licensed Apache-2.0. It adds 77 tokens to every session and 466 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to cdc-dibbs-design-system, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
cobejs
Use when adding a lightweight interactive globe with cobe (canvas setup, markers, interaction, performance, integration with React/Next.js).
stitch::react-components
Converts Stitch designs into modular Vite and React components, or syncs/updates existing React components to align with the latest Stitch designs, using system-level networking and AST-based validation.
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…