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/gate)<a href="https://agentmods.dev/skills/kmajerowicz/get-shit-right/gate"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/gate/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/gate"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/gate.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.00022 | $0.00713 |
| Opus 5.5 | $0.00009 | $0.00285 |
| Sonnet 5.5 | $0.00004 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
gsr-gate 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSR Gate Function
Configured checks establish observations, not human acceptance or deployment. Explicit authorization covers routine verification; host permissions still apply.
Discover and configure
Discover the canonical worktree and DOC_ROOT with ${CLAUDE_PLUGIN_ROOT}/lib/project.js. Read validated project-root .gsr.json (schemaVersion 1) for checks and profiles. Never infer initialization from a CLAUDE.md mention. If only a legacy ## Gate exists in DOC_ROOT/techstack.md, translate known commands against actual project scripts/configuration into .gsr.json during authorized work, preserving the prose and summarizing the change. Reconcile conflicts; missing or invalid configuration remains unverified. Do not invent npm, TypeScript or lint defaults.
Checks use nonempty argv arrays, project-relative cwd, required, timeoutMs and kind (static, test, runtime). Execution uses no shell. Split pipelines/operators into independent checks or a reviewed script that propagates failures. Do not install missing tools merely to make a check pass.
Run and read evidence
GSR invokes the internal runner (not a new user command):
node "${CLAUDE_PLUGIN_ROOT}/scripts/run-checks.js" --cwd "<canonical-project-root>"
# Add --profile <configured-name> only when its documented applicability covers this change.
Default selects all required checks. A docs-only profile is valid only with bounded documented applicability; uncertainty uses default. Never create a reduced profile to obtain a pass. Scale checks to changed behavior; an unrelated documentation edit does not universally require application/browser reruns. Reuse a prior run only after evidence freshness matches current project/configuration/requirements. Read ${CLAUDE_PLUGIN_ROOT}/lib/evidence.js for project-bound run records; latest relevant started run wins, including failure/interruption. Missing, corrupt, unsupported or stale evidence cannot establish passing verification. Legacy session gate JSON and tool/assistant prose are not 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 · -18 lines · -24 tokens per session a68f31a609f4
- 2mo ago First seen · 56 lines · 46 tokens per session scan A 548d0aae721d
gsr-gate is a skill published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 713 once invoked, about $0.0001 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
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.