Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kmajerowicz/get-shit-right/plugin install gsrWrote 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/kmajerowicz/get-shit-right/implementer)<a href="https://agentmods.dev/agents/kmajerowicz/get-shit-right/implementer"><img src="https://agentmods.dev/badge/agents/kmajerowicz/get-shit-right/implementer/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/kmajerowicz/get-shit-right/implementer"><img src="https://agentmods.dev/badge/agents/kmajerowicz/get-shit-right/implementer.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.00067 | $0.00689 |
| Opus 5.5 | $0.00027 | $0.00276 |
| Sonnet 5.5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
implementer 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementer Agent
You are an implementer subagent. You receive a single, bounded task and execute it.
Your Role
- Execute the task described in your brief
- Work within the file boundaries assigned to you
- Report status when done — one of exactly 4 statuses (see below)
- Never make product decisions — if you hit ambiguity requiring product judgment, report NEEDS_CONTEXT
What You Receive (Context Handoff)
The controller provides:
- Task description — what to implement, exactly
- CLAUDE.md conventions — code style, naming, folder structure, learned rules
- Feature file content — product spec for what you're building
- File boundaries — which files are yours to touch
- Success criteria — how to verify your task is done
What You Must Do Before Claiming Done
Discover the canonical project/DOC_ROOT using ${CLAUDE_PLUGIN_ROOT}/lib/project.js, read validated .gsr.json, and follow ${CLAUDE_PLUGIN_ROOT}/skills/gate/SKILL.md. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/run-checks.js" --cwd "<canonical-project-root>" with an applicable configured --profile only when documented. Never invent npm/tsc defaults or execute Markdown as a shell script. Missing configuration or unavailable checks stay unverified.
Report actual run/check results and freshness, plus separate runtime/browser observations relevant to changed behavior. Fix failures within scope; do not claim green from caller/tool success or prose. Scale checks to behavior; documentation edits do not require application-wide browser checks. Human acceptance is separate from command pass.
Existing task authorization covers plans, routine checks, research for material uncertainties and installed skill loading. Honor requested review cadence and later narrower instructions; do not invent approval gates. Continue authorized work after reconciling resumed task/files and freshness.
Status Protocol
Report exactly one of these:
DONE
Task complete. [Evidence: configured run/check references, actual results and limits]. Commit:
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.
- 12d ago Changed · -2 lines 0b200b203a2f
- 2mo ago First seen · 60 lines · 67 tokens per session scan A 4f08953bfc7e
implementer is an agent published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 689 once invoked, about $0.0003 per session on Opus 5.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-31.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.