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 instructions/jubscodes/get-shit-pretty/claude-mdgit 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/instructions/jubscodes/get-shit-pretty/claude-md)<a href="https://agentmods.dev/instructions/jubscodes/get-shit-pretty/claude-md"><img src="https://agentmods.dev/badge/instructions/jubscodes/get-shit-pretty/claude-md.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.02792 | $0.02792 |
| Opus 5 | $0.01396 | $0.01396 |
| Sonnet 5 | $0.00558 | $0.00558 |
| Haiku 4.5 | $0.00279 | $0.00279 |
Grade A, and why
get-shit-pretty CLAUDE.md 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSP — Get Shit Pretty
Must-always / Must-never
- Always edit source under
gsp/— never inside.claude/,.opencode/,.gemini/,.agents/,.codex/(symlinks or installer-managed). - Always put new package dependencies in
devDependencies— the npm package ships zero prod deps. - Always ship changes via PR —
mainis protected, no direct push. Squash-merge viagh pr merge --squash. - Never edit inside
.design/from a skill — it's user/agent output only. - Never add
model:oreffort:to skill frontmatter — model selection is the user's choice. - Never hardcode output paths in agents — use
"path provided by the skill that spawned you".
Design engineering system for Claude Code, OpenCode, Gemini, and Codex.
Git workflow
main is protected — all changes require a PR (no direct push). Use feature/release branches and squash merge via gh pr merge --squash.
This repository
This repo is both:
- Source and npm package — where the GSP agentic framework is built, versioned, and published via
npm publish. Thepackage.jsonfilesfield controls what ships:.mcp.json,bin,scripts,gsp. - GSP consumer — GSP is installed here too (e.g.
.claude/symlinks). You can run GSP workflows in this workspace while developing the framework.
Edit source under gsp/; the installer keeps runtimes in sync. Never edit inside .claude/ (or other runtime dirs) directly — they point at or are populated from source.
Architecture
Dual-diamond: Branding (discover → strategy → identity → patterns) + Project (brief → research → design → critique → build → review). Verbal identity is merged into brand-strategy (4 phases, not 5).
Two skill layers
Expertise skills (knowledge owners): gsp-color, gsp-typography, gsp-visuals, gsp-accessibility, gsp-style
Own domain knowledge as sibling files (domains/, references/). Serve the full pipeline, not just one phase. Two consumption patterns:
- Read (passive) — pipeline skill or agent reads expertise skill's sibling files for domain context
- Invoke (active) — pipeline skill calls the expertise skill to run its logic (e.g.
--enrich,--validate)
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 · 193 lines · 2,792 tokens per session scan A 0f282dd99ba8
get-shit-pretty CLAUDE.md is an instructions file published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 2,792 tokens to every session, about $0.0140 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 instructions, from other repositories
design-sandbox AGENTS.md
Instructions for memi-design/design-sandbox, covering this is not the next.js you know, design2code.ground, quick orientation and pointers for non-claude tools.
design-sandbox CLAUDE.md
Instructions for memi-design/design-sandbox, a project described as: memi-ready Next.js, Tailwind, shadcn, MCP, and Agent Skills sandbox for interface understanding and design-to-code exploration.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.