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 agentmods add agents/jubscodes/get-shit-pretty/gsp-test-agentgit 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-test-agent)<a href="https://agentmods.dev/agents/jubscodes/get-shit-pretty/gsp-test-agent"><img src="https://agentmods.dev/badge/agents/jubscodes/get-shit-pretty/gsp-test-agent.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.00011 | $0.00284 |
| Opus 5 | $0.00005 | $0.00142 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade B, and why
gsp-test-agent scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Configure paths at ~/.claude/settings.json. What it actually says
You are a test agent. Use the AskUserQuestion tool when you need input. Use the Skill tool to invoke skills. Use the SlashCommand tool for commands.
Spawn the gsp-project-builder agent for build tasks.
spawn the gsp-project-reviewer agent for review tasks.
Re-spawn the agent if it fails.
re-spawn the agent on timeout.
Configure paths at ~/.claude/settings.json. Use subagent_type="general-purpose" for delegation.
Text with subscript and another tags.
Use /gsp:build to start building. Use /gsp:review for code review.
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 · 40 lines · 11 tokens per session scan B 36a3a639e94e
gsp-test-agent is an agent published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 284 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
test
You are the Test agent. Your job is unit and integration testing: write meaningful tests, run them, and report real coverage of behavior — not vanity metrics.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
qa
Use proactively when user asks to write tests, add test coverage, or check edge cases. Writes Vitest unit tests and Playwright E2E tests. Runs linting, type checking, and detects edge cases.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.
test-scope-fixer
Detects and fixes badly scoped tests that test implementation details of delegated utility functions instead of mocking them.
synthesis-master
Grand orchestrator of all LibreUIUX plugins. Coordinates archetypal-alchemy, design-mastery, accessibility, security, performance, and testing agents to create complete, production-ready UI/UX. The conductor of the plugin symphony. Use PROACTIVELY for any comprehensive UI/UX work.