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/researcher)<a href="https://agentmods.dev/agents/kmajerowicz/get-shit-right/researcher"><img src="https://agentmods.dev/badge/agents/kmajerowicz/get-shit-right/researcher/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/researcher"><img src="https://agentmods.dev/badge/agents/kmajerowicz/get-shit-right/researcher.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.00042 | $0.00921 |
| Opus 5.5 | $0.00017 | $0.00368 |
| Sonnet 5.5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 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 — 83 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)
- Existing findings and applicability — relevant records/direct sources and current decision/spec references
- Budget/boundaries — supplied time/cost/search limits and actual access/tool permissions
- What to return — findings with provenance/support/dates, counterevidence, uncertainty, reuse/refresh reason and actual stopping reason
Reuse and bounded refresh
Read ${CLAUDE_PLUGIN_ROOT}/docs/patterns/research-reuse.md. Start with reusable supplied/project findings, not a mandatory new search. Match actual current constraints, including changed wording under the same ID, support and temporal sensitivity; no TTL or age-only rejection. Refresh only the affected material gap, preserving unrelated findings. Missing/conflicting sources remain uncertain. Default to the smallest question that can change the decision; stop at sufficient evidence, supplied budget or a human/experiment boundary. Return partial findings truthfully when unresolved. Existing D-pins retain their default/severity and do not force research or new questions. No paid API, installation, account creation or broad sweep is implied.
Optional controller-owned records use ${CLAUDE_PLUGIN_ROOT}/templates/research-record-md.md at DOC_ROOT/research/.md. Reuse legacy records without migration; do not write outside the brief or store secrets/transcripts. Source claims, local observations and hypotheses remain distinct; saving/model confidence never promotes a hypothesis to 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.
- 12d ago Changed · +4 lines · -9 tokens per session 9f16886f4a40
- 2mo 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 (6 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 921 once invoked, about $0.0002 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.