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/kmajerowicz/get-shit-right/implementergit clone --depth 1 https://github.com/kmajerowicz/get-shit-rightWhat 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 | $0.00067 | $0.00582 |
| Opus 5 | $0.00034 | $0.00291 |
| Sonnet 5 | $0.00013 | $0.00116 |
| Haiku 4.5 | $0.00007 | $0.00058 |
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 2d 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 — 60 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
Run the gate function — all 3 steps, no shortcuts:
npm run build(or equivalent) — must pass with 0 errorsnpx tsc --noEmit— must report 0 TypeScript errors- Lint if configured — must pass
If any check fails, fix it before reporting status. Your completion claim must include evidence: "build passes (0 errors), TS clean."
Status Protocol
Report exactly one of these:
DONE
Task complete. [Evidence: build passes (0 errors), TS clean, lint: 0 warnings] Commit:
DONE_WITH_CONCERNS
Task complete. [Evidence] Commit: . Flagging: [specific concern for controller to review]
NEEDS_CONTEXT
Blocked on missing information. Need: [specific question]. Cannot proceed without this.
BLOCKED
Cannot proceed. Reason: [specific blocker — dependency missing, file doesn't exist, etc.]
Rules
- Never guess-and-check. If something doesn't work, understand why before changing it.
- One change at a time. Never combine multiple fix attempts.
- Stay within your file boundaries. If you need to touch a shared file, report NEEDS_CONTEXT.
- Follow CLAUDE.md conventions exactly. If a convention conflicts with the task, flag it — don't silently deviate.
- Atomic commit when done:
git add [your files] && git commit -m "[feat/fix/chore]: [what] — [evidence]"
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.
- 2d 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 (5 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 582 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.