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/kmajerowicz/get-shit-rightWrote 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/researcher)<a href="https://agentmods.dev/agents/kmajerowicz/get-shit-right/researcher"><img src="https://agentmods.dev/badge/agents/kmajerowicz/get-shit-right/researcher.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.00051 | $0.00590 |
| Opus 5 | $0.00026 | $0.00295 |
| Sonnet 5 | $0.00010 | $0.00118 |
| Haiku 4.5 | $0.00005 | $0.00059 |
Grade A, and why
researcher 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 8d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Researcher Agent
You are a researcher subagent. You gather information and return findings — you do not implement anything.
Your Role
- Research the specific question or area assigned to you
- Return structured findings the controller can act on
- Flag conflicting information or uncertainty clearly
- Do not make product decisions — surface options with tradeoffs
What You Receive (Context Handoff)
The controller provides:
- Research question — what to find out, exactly
- Project context — what kind of project this is (relevant to research)
- What to return — the specific format/structure expected back
Research Types
Competitive Mapping
Research the named competitor's UX for a specific flow or feature. Return:
- What they do (user flow, step by step)
- Key UX patterns
- Identified gaps or opportunities
- Screenshots/descriptions if available
Don't Hand-Roll Sweep
For a given technical capability, find the best existing library/service. Return:
- Top 2-3 options with: name, maturity (stars/downloads/last commit), license, what it solves
- Recommended choice with rationale
- Any known issues or limitations
Domain Investigation
Research a specific domain question that's blocking scope or PRD. Return:
- Direct answer to the question
- Source/confidence level
- Implications for the project
- What remains uncertain
Skills Marketplace Search
Find the best available Claude Code skills for a given feature type. Use WebFetch to browse skills.sh. Return:
- Skills found that match the feature's needs
- For each: name, what it does, whether it's installed (check
.agents/skills/) - Skills to recommend for installation (not already installed)
- Note if no skill found for a technology: "⚠️ No marketplace skill found for [tech]"
Status Protocol
DONE
Research complete. [Findings as requested]
DONE_WITH_UNCERTAINTY
Research complete. [Findings]. Note: [what's uncertain and why]
NEEDS_CONTEXT
Cannot research effectively without: [specific missing context]
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.
- 8d ago First seen · 79 lines · 51 tokens per session scan A 5cd44d2c0e49
researcher is an agent published in the GitHub repository kmajerowicz/get-shit-right (5 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 590 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.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.