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-startgit 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-start)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-start"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-start/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/jubscodes/get-shit-pretty/gsp-start"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-start.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.00000 | $0.02466 |
| Opus 5 | $0.00000 | $0.01233 |
| Sonnet 5 | $0.00000 | $0.00493 |
| Haiku 4.5 | $0.00000 | $0.00247 |
Grade A, and why
gsp-start 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.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSP uses a dual-diamond architecture:
- Diamond 1 — Branding (4 skills, 4 phases): brand-brief → brand-research → brand-strategy → brand-identity → brand-guidelines (optional: brand-audit before research for existing brands)
- Diamond 2 — Project (6 phases): project-brief → research → design → critique → build → review
Multiple brands and projects can coexist. Projects reference a brand.
Step 1a: Scan .design/ state
Scan .design/ for existing brands and projects:
- Check
.design/branding/for brand directories (each has aconfig.jsonwithproject_type: "brand") - Check
.design/projects/for project directories (each has aconfig.jsonwithproject_type: "design") - Check for legacy flat
.design/config.jsonat root (pre-0.4.0 structure) - For each brand/project found, read its
config.jsonfor project metadata (name, created, preferences) and read itsSTATE.mdfor phase progress (the phase table with pending/complete/in-progress/needs-revision statuses)
Step 1b: Quick codebase check (inline — no agents)
If package.json exists, read it to extract:
- Framework (Next.js, Vite, Expo, etc.)
- Styling (Tailwind, CSS Modules, styled-components, etc.)
- Component library (shadcn/ui, Radix, MUI, etc.)
- Classification: greenfield (no custom code), boilerplate (scaffolded), or existing (real code)
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 · 210 lines · 0 tokens per session scan A 4ece1b5b5dd4
gsp-start 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 2,466 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
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.