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 gspdev-devgit 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/gspdev-dev)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-dev"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-dev/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/gspdev-dev"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-dev.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.00023 | $0.01294 |
| Opus 5.5 | $0.00009 | $0.00518 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (55 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 1,294 once invoked, about $0.0001 per session on Opus 5.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
alive:create-walnut
Something new is emerging. A venture, an experiment, a person entering the orbit, a life area getting serious. It needs its own walnut — its own identity, history, and future. Scaffolds the full structure, maps existing context sources, and optionally migrates files across.
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
alive-bundle
Create, manage, and graduate bundles -- the unit of focused work within a walnut.
alive-create
Scaffold a new walnut -- venture, experiment, person, life area, project.
alive-project
Regenerate now.json projections for all walnuts (mechanical, no approval needed).
technical-roadmap-planning
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.