Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add kmajerowicz/get-shit-right --skill feedbackgit clone --depth 1 https://github.com/kmajerowicz/get-shit-rightWrote 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/feedback)<a href="https://agentmods.dev/skills/kmajerowicz/get-shit-right/feedback"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/feedback/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/feedback"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/feedback.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.00043 | $0.00945 |
| Opus 5.5 | $0.00017 | $0.00378 |
| Sonnet 5.5 | $0.00009 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
gsr-feedback 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 2mo 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gsr:feedback — Feedback Skill
You are executing the /gsr:feedback command. Your job is to capture user feedback and write it to docs/BACKLOG.md.
Iron Laws
- One message, not twenty. Ask for all missing context in a single follow-up — never ping-pong the user.
- Don't interpret, capture. Write the feedback in the user's words, not a paraphrase. Add your classification alongside it.
- Always confirm what was written. Show the exact entry added to BACKLOG.md after writing it.
Step 1: Intake + Completeness Check
Read the user's feedback. Determine the type and check completeness against the requirements below.
Bug report — required fields:
- Area — which feature, screen, or flow
- What happened — the actual behavior observed
- What should have happened — the expected behavior
- Severity — how bad is it?
critical— blocks core functionality, no workaroundmajor— significantly impacts usability, workaround is painfulminor— inconvenient but doesn't block anything
Feature request — required fields:
- Area — which part of the product this relates to (or "new" if it doesn't exist yet)
- What — description of what the user wants
- Why — the problem it solves or the value it adds
Change request — required fields:
- Area — which feature or screen is affected
- Current behavior — what happens today
- Desired behavior — what should happen instead
- Why — reason for the change (UX issue, business need, user confusion, etc.)
If the type is ambiguous OR any required field is missing: ask once, combining all questions into a single message. Do not ask field by field.
If everything is clear from the user's message: skip to Step 2 without asking anything.
Step 2: Format the Entry
Use the format matching the type:
Bug
**[Short title]**
Area: [feature/screen/flow]
What happened: [actual behavior]
Expected: [expected behavior]
Severity: [critical / major / minor]
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.
- 2mo ago First seen · 150 lines · 43 tokens per session scan A bdd53ca02104
gsr-feedback is a skill published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 945 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…