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/commands/kmajerowicz/get-shit-right/verify)<a href="https://agentmods.dev/commands/kmajerowicz/get-shit-right/verify"><img src="https://agentmods.dev/badge/commands/kmajerowicz/get-shit-right/verify/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/commands/kmajerowicz/get-shit-right/verify"><img src="https://agentmods.dev/badge/commands/kmajerowicz/get-shit-right/verify.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.00014 | $0.00424 |
| Opus 5.5 | $0.00006 | $0.00170 |
| Sonnet 5.5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
verify 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.
This is a copy
86% identical to learn — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are running the /gsr:verify command.
Project discovery: Resolve the canonical project/worktree and DOC_ROOT with ${CLAUDE_PLUGIN_ROOT}/lib/project.js and validated .gsr.json. Invocation in a subdirectory or through a symlink does not require directory confirmation. Never silently follow an obsolete session manifest to a different project. Reconcile invalid configuration; ask only if the intended project is genuinely unresolved.
Session manifest: After confirming the working directory, write .gsr-session.json in the project root:
{ "project_dir": "<absolute path>", "project_name": "<from CLAUDE.md or scope>", "last_command": "gsr:verify", "timestamp": "<ISO 8601>" }
Update this file (don't recreate) if it already exists — reconcile project_dir/project_name with the canonical intended project rather than retaining stale identity; update command/time without overwriting unrelated fields.
Use $ARGUMENTS as the explicit target when supplied: a slug resolves to DOC_ROOT/features/.md, a relative spec uses task-handoff reference validation. Otherwise reconcile the latest request/saved task; do not select a whole PRD from a stale NOT STARTED label.
Load and execute the verification skill: read ${CLAUDE_PLUGIN_ROOT}/skills/verification/SKILL.md in full, then follow its instructions exactly.
At a major stage boundary, save the compact Active Task packet per
${CLAUDE_PLUGIN_ROOT}/docs/patterns/stage-handoff.md, including original scope/cadence,
actual result/limits and next authorized action. Recommend /clear then dalej
when another stage remains; direct next-stage commands are optional. Do not manufacture
implementation authority from a planning-only request or a verified check. If the task
is complete, report the result without inventing a next stage.
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 · +7 lines · -2 tokens per session 79c219240de1
- 2mo ago First seen · 19 lines · 16 tokens per session scan A a62b66c9a2cd
verify is a command published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 14 tokens to every session and 424 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to learn, differing in 24 lines, and is treated as a copy.
Other commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
check-dev
Type-check a Z specification with fuzz.