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-helpgit 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-help)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-help"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-help.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.00007 | $0.01123 |
| Opus 5 | $0.00003 | $0.00562 |
| Sonnet 5 | $0.00001 | $0.00225 |
| Haiku 4.5 | $0.00001 | $0.00112 |
Grade A, and why
gsp-help 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output ONLY the reference content below. Do NOT add:
- Project-specific analysis
- File context or git status
- Next-step suggestions
- Any commentary beyond the reference
GSP version: !cat ${CLAUDE_SKILL_DIR}/../../VERSION 2>/dev/null || echo "0.4.3"
Output the reference
Output the following as plain text. Use Unicode characters (───, ◇, ├──, └──, │, →) for visual structure.
Skill names are left-padded with 4 spaces. Descriptions start at column 27 (4 indent + 23 max skill name width).
/gsp- ◇◇ v{VERSION}
skill reference
─── Getting Started ──────────────────
/gsp-start start here — picks up where you left off
/gsp-help this skill reference
/gsp-progress how pretty are we?
─── Branding ─────────────────────────
/gsp-brand-brief define your brand through guided Q&A
/gsp-brand-research research your market and audience
/gsp-brand-strategy define positioning, personality, voice and messaging
/gsp-brand-identity create visual identity
/gsp-brand-guidelines build design system tokens and components
/gsp-brand-sync sync brand to match a project's shipped state
/gsp-brand-refine tweak brand tokens mid-project without re-running identity
/gsp-brand-audit audit existing brand before evolving (optional)
─── Project ──────────────────────────
/gsp-project-brief scope what you're building
/gsp-project-research research UX patterns and approaches
/gsp-project-design design screens and flows
/gsp-project-critique critique designs + accessibility audit
/gsp-project-build implement designs in the codebase
/gsp-project-review QA validate implementation against designs
/gsp-add-reference add reference material to a project
─── Expertise ───────────────────────
/gsp-color color systems — palettes, contrast, semantic mapping, dark mode
/gsp-typography type systems — scale, pairing, fluid type, vertical rhythm
/gsp-visuals visual direction — imagery, 3D, video, textures
/gsp-icons icon systems — library, sizing, containers, custom SVG
/gsp-logo logo directions — concepts, variations, usage rules
/gsp-accessibility contrast, tokens, design/code audit, statement
/gsp-style apply a design style preset
─── Utilities ────────────────────────
/gsp-design-system scan and document existing design system state
/gsp-scaffold deterministic stack setup — deps, configs, verify build
/gsp-doctor check project health
/gsp-update update GSP to latest version
─── Easter Eggs ────────────────────
/gsp-art ASCII art studio
/gsp-pretty surprise terminal art
─── Flow ─────────────────────────────
brand first, then build.
— or —
quick mode: pick a style → jump straight to project.
branding brief → research → strategy → identity → guidelines
project brief → research → design → critique → build → review
↑ ↑
critique loop QA loop
quick style → brief → research → design → critique → build → review
run any skill directly — routing is optional.
─── Directory Structure ──────────────
.design/
├── branding/
│ └── {brand}/
│ ├── config.json brand config
│ ├── STATE.md progress tracking
│ ├── discover/ research chunks
│ ├── strategy/ strategy + voice and messaging
│ ├── identity/ visual identity
│ └── system/ tokens + components
└── projects/
└── {project}/
├── config.json project config
├── STATE.md progress tracking
├── brand.ref brand reference
├── brief/ scope + adaptations
├── research/ UX + tech research
├── design/ screen specs + preview
├── critique/ design critique
├── build/ BUILD-LOG.md
├── review/ QA acceptance
├── references/ custom reference material
└── exports/INDEX.md chunk index
get-shit-pretty v{VERSION}
github.com/jubscodes/get-shit-pretty
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 · 129 lines · 7 tokens per session scan A 00aed03da432
gsp-help is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 7 tokens to every session and 1,123 once invoked, about $0.0000 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-30.
Other skills, from other repositories
opencli-usage
Use at the start of any OpenCLI session — this is the top-level map of what opencli can do, how to discover adapters, what flags and output formats are universal, and which specialized skill to load next. Point here when an agent asks "what can opencli do?" or "how do I find the right command?".
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
opencli-browser-sitemap
Use when driving a website with opencli browser and sitemap context is available, requested, or needed to avoid blind navigation. Guides agents to consume site sitemap files lazily, choose adapter/browser fallback paths, resume from state signatures, and mark stale sitemap entries without trusting them over live…
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
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.
gpt-vis
A chart-generation tool that recommends visual formats for data and produces either chart settings or runnable code. It uses GPT-Vis, a library for rendering data visualisations.