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-phase-transitiongit 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-phase-transition)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-phase-transition"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-phase-transition/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-phase-transition"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-phase-transition.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.00028 | $0.00816 |
| Opus 5 | $0.00014 | $0.00408 |
| Sonnet 5 | $0.00006 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00082 |
Grade A, and why
gsp-phase-transition 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 11d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The calling skill provides phase name and output directory. This skill reads STATE.md, renders the transition, and returns. The calling skill handles routing (AskUserQuestion, E2E auto-invoke, etc.) after this skill completes.
Input: Phase name + output directory path from the invoking skill Output: Terminal output with pipeline progress, completion banner, and file tree Agent: None — inline rendering
The invoking skill provides:
- Phase name — which phase just completed (e.g., "discover", "strategy", "build")
- Output directory — path to the phase's output files
Look up the completion message from the defaults table. If the invoking skill provided a custom message, use that instead.
Step 1: Read STATE.md
Determine context by reading the brand or project STATE.md:
- Which pipeline (branding or project)?
- Which phases are complete?
- Brand/project name?
Use Glob to find STATE.md: .design/branding/*/STATE.md or .design/projects/*/STATE.md.
Step 2: Pipeline progress line (conditional)
Show the pipeline line only when 2+ phases are complete. If this is the first phase completed, skip the pipeline line.
Styling
◆for completed phases◈for next phase◇for pending phases───connecting phases
{brand-or-project-name}
◆ discover ─── ◆ strategy ─── ◈ identity ─── ◇ guidelines
Branding phases
discover ─── strategy ─── identity ─── guidelines
If audit phase exists (evolve mode), prepend: audit ───
Project phases
brief ─── research ─── design ─── critique ─── build ─── review
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.
- 11d ago First seen · 122 lines · 28 tokens per session scan A d0fb98a8ba71
gsp-phase-transition is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 816 once invoked, about $0.0001 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…
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.
infographic-creator
Create beautiful infographics based on given text content. Use when users request to create infographics.
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.