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 agentmods add commands/kmajerowicz/get-shit-right/statusgit 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/commands/kmajerowicz/get-shit-right/status)<a href="https://agentmods.dev/commands/kmajerowicz/get-shit-right/status"><img src="https://agentmods.dev/badge/commands/kmajerowicz/get-shit-right/status.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00651 |
| Opus 5 | $0.00009 | $0.00326 |
| Sonnet 5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
status 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the /gsr:status command.
Working directory check: If .gsr-session.json exists and project_dir points to a different directory than pwd, cd there first.
Look for docs/STATE.md in the current working directory.
If STATE.md does not exist
Also check if docs/scope.md exists — if it does, suggest /gsr:prd. Otherwise:
No STATE.md found. Run
/gsr:scopeto start a new project, or/gsr:learnif you have an existing codebase.
Stop here — do not continue.
If STATE.md exists
Parse it and output a structured status report using this exact format:
Project: [project name from STATE.md header] Status: [Project Status value] Last Updated: [Last Updated value]
Phase Progress
[Reproduce the phase table from STATE.md, or "No phases defined yet." if missing]
Current Feature Progress
[Reproduce the active feature table (the one for the current/most-recent phase), or "No features in progress." if missing]
Next Action
[Next Action value from STATE.md]
Blockers
[List any features with status BLOCKED, or phases with status BLOCKED. If none, write "None."]
Open Assumptions
[Count + IDs of ledger rows with Status assumed from PRD.md, oldest first,
e.g. "2 open: project.D1 (paper sizes), project.D3 (pricing tier)". If PRD.md
or the ledger is missing, write "None."]
Deferred to Backlog
[List items from the Deferred section, or "None." if empty]
Suggested Command
[Derive from STATE.md using this logic:]
- If all phases show PASS and backlog is triaged → "Project complete. Nothing to do."
- If any phase shows VERIFYING →
/gsr:verify - If any phase shows BUILDING or any feature is in progress →
/gsr:build - If phases exist but all are NOT STARTED →
/gsr:build(pick first feature from Phase 1) - If no phases exist but scope.md exists →
/gsr:prd - If no scope.md exists →
/gsr:scope
Active Sessions
Scan docs/debug/ for files with status: active in frontmatter. Scan docs/plans/ for files with status: in_progress in frontmatter. For each found, show one line:
- Debug:
docs/debug/<slug>.md— feature: , last updated: - Plan:
docs/plans/<slug>.md— / tasks done, last updated:
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.
- 4d ago First seen · 68 lines · 17 tokens per session scan A 3aca2f731be2
status is a command published in the GitHub repository kmajerowicz/get-shit-right (5 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 651 once invoked, about $0.0001 per session on Opus 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].