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 agentmods add skills/jubscodes/get-shit-pretty/gsp-progressnpx skills add jubscodes/get-shit-pretty --skill gsp-progressgit 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-progress)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-progress"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-progress.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.01598 |
| Opus 5 | $0.00000 | $0.00799 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
gsp-progress 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 6d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output as plain text using Unicode characters for visual hierarchy:
- Diamonds:
◆complete,◈active/in-progress,◇pending - Dividers:
─── Label ──────────────────as section separators - Pipeline flow: phases connected by
───, diamond prefix per phase - Progress bar:
████████░░░░░░░░░░░░ 40% (2/5)— bar width 20 chars, filled =Math.round(20 * completed / total) - Tree connectors:
├──,└──,│for file listings - Arrows:
→for next skill routing
Check .design/branding/ for brand directories and .design/projects/ for project directories.
If neither found, check for legacy .design/STATE.md:
- If found: show legacy progress
- If not: display the empty state (see below)
Step 2: Read state for each instance
For each brand: read STATE.md and config.json
For each project: read STATE.md, config.json, and brand.ref
Count chunks per phase: count .md files in each phase directory (excluding INDEX.md).
Step 3: Calculate prettiness
Brands: count completed/skipped phases out of 4 Projects: count completed/skipped phases out of 6
Determine the Brand Mark diamond states:
- First diamond = branding status (highest across all brands):
◇none,◈in progress,◆all complete - Second diamond = project status (highest across all projects):
◇none,◈in progress,◆all complete
Step 4: Validate state integrity
For each phase marked as complete in STATE.md, verify the phase directory contains at least 1 chunk file. If status === 'complete' and chunk count is 0, display that phase as ◆! with note "(empty — may need re-run)".
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.
- 6d ago First seen · 186 lines · 0 tokens per session scan A 252c2539b3ce
gsp-progress 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,598 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
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-scan-code-accessibility
Scan generated/authored HTML for accessibility violations with axe-core (Deque) running over JSDOM — structural and semantic rules: ARIA attributes and roles, accessible names, alt text, form labels, heading order, landmarks, semantic HTML, tabindex, duplicate IDs, lang attribute, and 50 more. Use on the CODE side of…
figma-import-tokens
Push design tokens from code INTO Figma as variables — DTCG / tokens.json / a token object → Figma variable collections, modes, and values. Use when the user wants to sync tokens code→Figma: triggers 'import tokens into Figma', 'create Figma variables from my tokens.json / DTCG / Tailwind config', 'sync design tokens…
figma-analyze-component-set
Analyze a Figma COMPONENTSET as a state machine for code generation — extract variant axes (state/size/etc.), map state variants to CSS pseudo-classes (hover→:hover, focus→:focus-visible, disabled→:disabled, error→[aria-invalid]), and compute per-variant visual diffs (only what changes per state). Use when generating…