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.
git 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/agents/jubscodes/get-shit-pretty/gsp-project-reviewer)<a href="https://agentmods.dev/agents/jubscodes/get-shit-pretty/gsp-project-reviewer"><img src="https://agentmods.dev/badge/agents/jubscodes/get-shit-pretty/gsp-project-reviewer/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/agents/jubscodes/get-shit-pretty/gsp-project-reviewer"><img src="https://agentmods.dev/badge/agents/jubscodes/get-shit-pretty/gsp-project-reviewer.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.00025 | $0.00088 |
| Opus 5 | $0.00013 | $0.00044 |
| Sonnet 5 | $0.00005 | $0.00018 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
gsp-project-reviewer 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 10d 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.
What it actually says
QA validates actual codebase implementation against design intent. Methodology provided by spawning skill.
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.
- 10d ago First seen · 13 lines · 25 tokens per session scan A ae3b35c65982
gsp-project-reviewer is an agent published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 88 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 agents, from other repositories
api-reviewer
Reviews API-facing changes for breaking edits and missing docs.
canvas-to-code-auditor
Read-only codebase audit for the target surface declared in Gate 0. Returns route status, components/hooks/lib used, sub-routes, and behaviors to port.
canvas-to-code-reviewer
Validates a single slice PR diff against the plan's slice spec. Returns PASS/REVISE with citations. Read-only — never pushes fixes.
code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2025/2026 best practices. Use PROACTIVELY for code quality assurance.
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
Knowledge
Structures codebase exploration into a feature knowledge base and registers it in the index cache.