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-logogit 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-logo)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gsp-logo"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-logo/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-logo"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gsp-logo.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.01600 |
| Opus 5 | $0.00000 | $0.00800 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
gsp-logo 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 10d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is a standalone composable skill. It works two ways:
- Standalone — user runs
/gsp-logodirectly for logo exploration - As a building block — the creative-director invokes this during the branding diamond to produce
logo-directions.md
A logo system is more than a mark — it's a flexible identity that works at every size (favicon to billboard), in every context (light, dark, monochrome), and in every variation (primary, secondary, icon, wordmark).
Input: Brand context (strategy, archetype, name) or user description
Output: logo-directions.md chunk with 3 directions, each with concept, rationale, variations, and usage rules
Agent: None — inline skill with structured questioning
<execution_context> @${CLAUDE_SKILL_DIR}/chunk-format.md </execution_context>
| Input | Mode |
|---|---|
/gsp-logo --enrich |
Enrich existing logo-directions.md |
/gsp-logo |
Interactive — design logo directions |
Enrich mode (--enrich)
Read existing {BRAND_PATH}/identity/logo-directions.md. For each direction, enrich with:
- Detailed construction geometry (grid, proportions, key relationships)
- Complete variation specs (primary, secondary, icon, wordmark, monochrome, reversed)
- Clear space rules expressed as fraction of mark height
- Minimum size calculations (full lockup vs icon breakpoint)
- Don'ts with specific examples
What ships with it
1 file 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.
- 10d ago First seen · 173 lines · 0 tokens per session scan A 755bf6e4cb73
gsp-logo 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,600 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
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.
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…