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-changeloggit 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-changelog)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-changelog"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-changelog/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-changelog"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-changelog.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.00038 | $0.01530 |
| Opus 5 | $0.00019 | $0.00765 |
| Sonnet 5 | $0.00008 | $0.00306 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
gspdev-changelog 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The project uses conventional-ish commit prefixes that map to changelog sections:
| Commit prefix | Changelog section | Notes |
|---|---|---|
feat: |
Added | New features and capabilities |
fix: |
Fixed | Bug fixes |
refactor: |
Changed | Restructuring, renames, migrations |
docs: |
(omit) | Documentation-only changes — skip unless user-facing |
chore: |
(omit) | Internal maintenance — skip unless notable |
perf: |
Changed | Performance improvements |
deprecate: |
Deprecated | Features marked for removal |
security: |
Security | Vulnerability fixes |
| No prefix | Changed | Default bucket for untagged commits |
CHANGELOG.md structure:
# Changelog
All notable changes to get-shit-pretty are documented here.
## [Unreleased]
### Added
- ...
## [X.Y.Z] — YYYY-MM-DD
### Added
- ...
Key rules:
[Unreleased]section always sits at the top, accumulating changes until release- Empty sections are omitted — don't include
### Fixedif nothing was fixed - Each entry is a single bullet: concise, human-readable, no commit hashes
- Group related commits into one entry (e.g. 5 refactor commits about skills → one "Refactored from commands to skills-only architecture" entry)
- The changelog is for users — internal plumbing details (CI, dev scripts, test changes) are omitted unless they affect the user experience
- update (default) — scan commits since last release, update the
[Unreleased]section - release — promote
[Unreleased]to a versioned section using the current VERSION - rebuild — regenerate the full changelog from git history (destructive, confirm first)
Step 0: Parse mode
$ARGUMENTS:
updateor empty — update the Unreleased section from recent commitsrelease— promote Unreleased to versioned releaserebuild— regenerate full changelog from git tags and history
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 · 168 lines · 38 tokens per session scan A 9fbf7dfaaf31
gspdev-changelog is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 38 tokens to every session and 1,530 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
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.