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/scope-shaping)<a href="https://agentmods.dev/skills/kmajerowicz/get-shit-right/scope-shaping"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/scope-shaping/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/scope-shaping"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/scope-shaping.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.00047 | $0.05279 |
| Opus 5.5 | $0.00019 | $0.02112 |
| Sonnet 5.5 | $0.00009 | $0.01056 |
| Haiku 4.5 | $0.00005 | $0.00528 |
Grade A, and why
gsr-scope 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gsr:scope — Scope Shaping Skill
You are executing the /gsr:scope command. Your job is to shape a new product/materials into DOC_ROOT/scope.md, or prepare one focused feature contract for an existing product (Start C). Choose by the requested outcome and actual code, not by missing whole-product PRD.
Fresh-context stage handoff
At a major stage or long-build increment, follow
${CLAUDE_PLUGIN_ROOT}/docs/patterns/stage-handoff.md. Save objective/constraints,
original authorization/latest cadence, actual completed/remaining work, open choices,
current evidence/run limits, stage/checkpoint, exact next step/action and minimal read
references in the existing Active Task. Keep requirements in covered source documents.
Recommend /clear then dalej after saving. The next context loads coordinate and
the selected current guidance/refs only after the user's continuation; no automatic
hook execution, context reset or new session. Direct commands remain scoped optional
controls. A completed task or tiny correction needs no new-stage/reset instruction.
Planning-only completion records no authorized implementation next step. Partial/checked
build increments preserve actual overall in-progress state, limits and requested review.
Focused task contract
Read ${CLAUDE_PLUGIN_ROOT}/docs/patterns/task-handoff.md when preparing/consuming a
nontrivial existing-product feature. A sufficient feature spec is the build contract;
missing whole-product PRD is not a blocker. Quick/read-only tasks need no scaffolding.
Use supplied constraints and actual code; retain valid deferrals and IDs. The optional
${CLAUDE_PLUGIN_ROOT}/lib/task-handoff.js provides structural observations only,
never semantic readiness, authority, passing behavior or acceptance.
Product demonstration when useful
For an explicit "show it before building" request or a concrete flow/visual/interaction/
technical uncertainty, load ${CLAUDE_PLUGIN_ROOT}/skills/preview/SKILL.md and follow
${CLAUDE_PLUGIN_ROOT}/docs/patterns/product-preview.md. Choose one useful demonstration
from actual uncertainty; skip clear corrections and ordinary work with established
patterns unless requested. Goal and main action are enough to start a bounded preview
before full PRD. A focused existing-product feature needs no whole-product PRD.
Planning-only stays planning; diagram-only creates no application code; preview-only
is not full implementation. Preserve show-and-wait across resets. Reuse settled inputs,
record observations vs simulations and update only affected requirements from feedback.
Do not introduce a public preview command/flag or make --sketch request a prototype.
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 · +36 lines 60e765f32f34
- 2mo ago First seen · 296 lines · 47 tokens per session scan A e3b5490a1ff7
gsr-scope is a skill published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 5,279 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.