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/skills/kmajerowicz/get-shit-right/quick)<a href="https://agentmods.dev/skills/kmajerowicz/get-shit-right/quick"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/quick/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/skills/kmajerowicz/get-shit-right/quick"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/quick.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.00056 | $0.01039 |
| Opus 5.5 | $0.00022 | $0.00416 |
| Sonnet 5.5 | $0.00011 | $0.00208 |
| Haiku 4.5 | $0.00006 | $0.00104 |
Grade A, and why
gsr-quick 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gsr:quick — Quick Task Skill
One bounded task, GSR invariants, zero ceremony. No scope, no PRD, no feature file, no mode selection, no skills-matching gate.
Collaboration contract
Explicit task authorization and constraints override generic workflow defaults within host permissions. Read settled answers from the conversation and project files; never ask for them again. A planning-only request does not authorize implementation. Prepare plans, research material uncertainties, load installed skills, record state and run proportionate checks without separate approval. Weight controls rigor, not authority or review cadence. Honor explicitly requested per-chunk review and later instructions narrowing autonomy; otherwise continue reversible work in scope. Ask only for an unresolved consequential product choice or a real installation, spending, publishing, destructive-action or host permission boundary. Continue independent authorized work while a decision is pending. Completion reports give the outcome, brief verification and unresolved limits; detailed evidence stays accessible.
Discover the canonical project and DOC_ROOT using ${CLAUDE_PLUGIN_ROOT}/lib/project.js and validated .gsr.json; below, docs/ means that resolved DOC_ROOT, not an assumed folder. Invalid discovery/configuration is a diagnostic to reconcile, never permission to silently switch projects.
Task continuation and completion
When authorized work updates STATE, add/update one optional ## Active Task section
without rewriting unrelated sections. Record objective, constraints, authorized scope,
source/date of authorization in prose, explicit review cadence, current plan/task relative
to DOC_ROOT, last verified run reference and next action. The template is
${CLAUDE_PLUGIN_ROOT}/templates/state-md.md; legacy files remain valid.
On resume read this section by heading (not the first 20 lines), read the referenced current task/plan, inspect actual repository state and observe current evidence freshness. Reconcile missing references and conflicting recorded progress with files; a done box is not proof and stale tests do not reset implemented work. Resume remaining authorized work without re-asking settled decisions. Preserve explicitly requested review boundaries; later instructions narrowing autonomy override STATE. No session record expands authority.
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 · +22 lines 222e49565b0e
- 2mo ago First seen · 52 lines · 56 tokens per session scan A 26640455f377
gsr-quick is a skill published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 56 tokens to every session and 1,039 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…