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 jubscodes/get-shit-pretty --skill gsp-accessibilitygit clone --depth 1 https://github.com/jubscodes/get-shit-prettyWrote 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/jubscodes/get-shit-pretty/gsp-accessibility)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-accessibility"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-accessibility.svg" alt="Measured on agentmods" 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.00000 | $0.01288 |
| Opus 5 | $0.00000 | $0.00644 |
| Sonnet 5 | $0.00000 | $0.00258 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
gsp-accessibility 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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Two consumption patterns:
- Standalone — user runs
/gsp-accessibilityand the skill picks the right mode from project state, or runs an explicit--mode - As a building block —
gsp-brand-guidelinescalls--validateas a pre-emit gate;gsp-project-critiqueandgsp-project-reviewreuse the chunks this skill writes
Accessibility runs at multiple checkpoints in the pipeline (brand emit, post-design, post-build, pre-ship). The mode determines which checkpoint.
Input: Mode flag (or none — auto-pick) + optional arguments
Output: Display, chunk file, statement, or audit log depending on mode
Agent: gsp-accessibility-auditor (only in --design and --code modes)
Read $ARGUMENTS to determine the mode:
| Input | Mode | Sibling | Agent? | Output |
|---|---|---|---|---|
--check #FG #BG |
Quick contrast | modes/check.md |
No | Display only |
--validate <yml> |
Pre-emit WCAG gate | modes/validate.md |
No | Stdout verdict + <yml-dir>/wcag-validate.log |
--tokens |
Brand token audit | modes/tokens.md |
No | critique/accessibility-token-audit.md |
--design |
Design screen audit | modes/design.md |
Yes | critique/accessibility-audit.md + fixes |
--code |
Codebase audit | modes/code.md |
Yes | review/accessibility-audit.md + fixes |
--statement |
Compliance statement | modes/statement.md |
No | exports/accessibility-statement.md |
| (no args) | Context-aware default | — | depends | depends |
Additional flag: --level AAA overrides conformance level (default: AA).
What ships with it
9 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.
- 8d ago First seen · 97 lines · 0 tokens per session scan A 92c66f7e6799
gsp-accessibility is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,288 tokens. 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
antv-x6-editor
A skill for creating and troubleshooting interactive diagrams with AntV X6, a JavaScript engine for editors made of connected nodes and lines. It supports diagram types such as flowcharts, dependency graphs, entity-relationship diagrams, and organization charts.
infographic-creator
Create beautiful infographics based on given text content. Use when users request to create infographics.
icon-retrieval
Search icons through HTTP API and retrieve SVG strings with curl.
ppt-orchestrator
A dispatcher for creating presentations, slide decks, long images, and weekly reports. It chooses a visual style and output format, then sends the work to a more specialised add-on.
zhongguose-html-skill
An HTML-only presentation system using traditional Chinese colours and Chinese-style visual design. It helps organise source material into a report structure and produces a self-contained HTML file with its assets.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…