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-publishWrote 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-publish)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-publish"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-publish/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-publish"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-publish.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.00028 | $0.01632 |
| Opus 5 | $0.00014 | $0.00816 |
| Sonnet 5 | $0.00006 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
gspdev-publish 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 9d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository: jubscodes/get-shit-pretty
Version is tracked in two files that must agree:
VERSION— single version string (novprefix)package.json→"version"
GitHub releases use v-prefixed tags (e.g., v0.5.2).
Step 1: Resolve version
If $ARGUMENTS contains a version string, use it. Otherwise, use AskUserQuestion to ask for the target version.
Read the current version from VERSION. Validate that the new version is higher than the current one (semver comparison).
Show:
─── Publish ────────────────────────────
Current: {current version}
Target: {new version}
Step 2: Pre-flight checks
Run these checks before changing anything. Abort on failure.
2a: Clean working tree
git status --short
If there are uncommitted changes, tell the user to commit or stash first. Abort.
2b: On main branch
git branch --show-current
If not on main, switch to main and pull: git checkout main && git pull origin main. The release commit will go through a PR branch anyway (main is protected).
2c: Up to date with remote
git fetch origin main && git rev-list HEAD..origin/main --count
If behind, tell the user to pull first.
Step 3: Bump versions
Update all three files:
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.
- 9d ago First seen · 236 lines · 28 tokens per session scan A e2f47da66f1d
gspdev-publish is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 1,632 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
git-flow-pr
Executes the full PR-driven development workflow: create an isolated feature branch from the current work, commit all staged changes, rebase cleanly onto the selected base branch (skipping any ancestor commits already merged), push the branch, and open a GitHub pull request linked to a related issue. Includes guidance…
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.
verify-cli
Run smoke tests against the mpak CLI to verify all commands work correctly before publishing a new release.
od-plugin-publish-github
Publish a local Open Design plugin to a new public GitHub repository using gh CLI.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.