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 skills/jubscodes/get-shit-pretty/gspdev-devnpx skills add jubscodes/get-shit-pretty --skill gspdev-devgit clone --depth 1 https://github.com/jubscodes/get-shit-prettyWhat 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 | $0.00023 | $0.01294 |
| Opus 5 | $0.00012 | $0.00647 |
| Sonnet 5 | $0.00005 | $0.00259 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
gspdev-dev 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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository: jubscodes/get-shit-pretty
Step 1: Gather state
Run these in parallel:
gh api repos/jubscodes/get-shit-pretty/milestones --jq '.[] | {title, number, open_issues, closed_issues, description}'
gh issue list --state open --json number,title,labels,milestone,assignees,createdAt,updatedAt --jq '.[] | {number, title, labels: [.labels[].name], milestone: .milestone.title}'
git log main..HEAD --oneline
git status --short
Step 2: Parse focus
$ARGUMENTS determines what to show:
allor empty — full analysis + recommendationmilestone— milestone progress onlyblockers— issues blocking other issuesready— issues ready to start (no dependencies, no blockers)
Step 3: Analyze issues
For each open issue in the active milestone, classify:
3a: Dependency graph
Read issue bodies to extract Related / Blocks / Depends on references. Build a lightweight dependency picture:
- Which issues block others?
- Which issues are leaf nodes (no dependencies)?
3b: Branch coverage
Cross-reference open issues against commits on the current branch (git log main..HEAD). Classify each issue as:
- Done on branch — commits clearly address this issue
- In progress — partial commits exist
- Not started — no related commits
3c: Effort signal
Estimate relative size from issue body:
- S — single file change, config, or docs
- M — multiple files, one workstream
- L — cross-cutting, new architecture pattern
3d: Impact signal
Rate based on what the issue unblocks:
- High — blocks 2+ other issues or is required for milestone completion
- Medium — blocks 1 issue or fills a gap
- Low — standalone improvement
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.
- 3d ago First seen · 164 lines · 23 tokens per session scan A 876cba4918e1
gspdev-dev is a skill published in the GitHub repository jubscodes/get-shit-pretty (53 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 1,294 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
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…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…