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/coordinate)<a href="https://agentmods.dev/skills/kmajerowicz/get-shit-right/coordinate"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/coordinate/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/coordinate"><img src="https://agentmods.dev/badge/skills/kmajerowicz/get-shit-right/coordinate.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.00060 | $0.01961 |
| Opus 5.5 | $0.00024 | $0.00784 |
| Sonnet 5.5 | $0.00012 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
coordinate 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task coordination across fresh contexts
Use for a GSR task request or an unambiguous saved-task continuation. This is
agent guidance over existing skills, not a classifier or automatic runtime.
Explicit commands and the latest user intent take precedence. Read
${CLAUDE_PLUGIN_ROOT}/docs/patterns/task-coordination.md for the route/boundary
contract and ${CLAUDE_PLUGIN_ROOT}/docs/patterns/task-handoff.md for features.
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.
Relevant installed skills
Read ${CLAUDE_PLUGIN_ROOT}/docs/patterns/skill-selection.md when selecting or
resuming guidance. Use the host's current catalog and actual task/output, load the
applicable SKILL.md, and reuse current guidance without redundant marketplace searches.
A saved skill name or a keyword match is not proof of use. Record only useful source/
provider/applicability/version-or-identity/loaded-use observations in existing feature/
plan sections; unknown identity stays unknown. Check availability/current content at
resume. Optional missing guidance permits authorized work; an essential missing capability
requires only its actual access/install boundary. Denied installation is not retried
through another downloader. No silent spending, publication or model switching.
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 First seen · 132 lines · 60 tokens per session scan A bfdd7846ffaa
coordinate is a skill published in the GitHub repository kmajerowicz/get-shit-right (6 stars, last pushed 2d ago), licensed MIT. It adds 60 tokens to every session and 1,961 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-10-20.
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,"…