Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jubscodes/get-shit-prettynpx agentmods add skills/jubscodes/get-shit-pretty/gspdev-auditWrote 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-audit)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-audit"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-audit.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.00039 | $0.03203 |
| Opus 5 | $0.00019 | $0.01602 |
| Sonnet 5 | $0.00008 | $0.00641 |
| Haiku 4.5 | $0.00004 | $0.00320 |
Grade A, and why
gspdev-audit 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source layout:
gsp/skills/— 34 skills (SKILL.md files, gsp-* prefixed dirs, withdomains/andreferences/siblings)gsp/agents/— 11 agents (gsp-*.md stub files, methodology in skills)gsp/templates/— config, state, brief, roadmap templatesbin/install.js— multi-runtime installerVERSION,package.json— version sources
Runtime compatibility reference: ${CLAUDE_SKILL_DIR}/../gspdev-runtime-compat/references/baseline.md
Step 0: Run automated tests
Run the test suite first — it covers versions, contracts, installer, runtime, and templates:
bash dev/scripts/audit-tests.sh $ARGUMENTS
The script accepts: all (default), versions, contracts, installer, runtime, templates.
Review the output. If all tests pass, report the clean result. If any tests fail or warn, investigate each issue using the deeper analysis steps below.
Step 1: Parse scope
$ARGUMENTS determines which checks to run:
allor empty — run everythingcontracts— agent↔skill contract checks onlyinstaller— installer correctness checks onlyruntime— runtime compatibility checks (uses gspdev-runtime-compat baseline)versions— version sync checks onlytemplates— template coherence checks only
Step 2: Version Sync (V)
Two version sources must agree:
cat VERSION
node -e "console.log(require('./package.json').version)"
V1: Version agreement — both match → PASS, mismatch → FAIL.
V2: CHANGELOG coverage — CHANGELOG.md has an entry for the current version → PASS, missing → WARN.
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 · 296 lines · 39 tokens per session scan A 4a712f1bbd96
gspdev-audit is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 3,203 once invoked, about $0.0002 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-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
mcpls
Install, configure, and run the mcpls CLI — a Rust binary bridging MCP to LSP that gives an agent compiler-grade code intelligence (hover, definitions, references, diagnostics, rename). Use when setting up or registering mcpls as an MCP server, writing or debugging an mcpls.toml, choosing CLI flags or MCPLS…
environment-diagnostics
Environment variable validation and configuration verification. Checks that required variables are set, config files parse correctly, ports are available, and system dependencies meet version requirements.
patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
od-code-migration
Default reference pipeline for the code-migration taskKind — code-import → design-extract → token-map → rewrite-plan → patch-edit ↔ build-test devloop → diff-review → handoff.
module-federation
Add, review, or debug client-rendered Module Federation support in Rsbuild-first TypeScript applications. Covers host/remote roles, exposes, remotes, shared dependencies, generated types, runtime loading failures, and observability checks.