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 shousper/claude-kit --skill setupgit clone --depth 1 https://github.com/shousper/claude-kitWrote 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/shousper/claude-kit/setup)<a href="https://agentmods.dev/skills/shousper/claude-kit/setup"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/setup/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/shousper/claude-kit/setup"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/setup.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.00137 | $0.01550 |
| Opus 5.5 | $0.00055 | $0.00620 |
| Sonnet 5.5 | $0.00027 | $0.00310 |
| Haiku 4.5 | $0.00014 | $0.00155 |
Grade A, and why
setup 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Workflow Setup
An interview, then story init writes everything. Never hand-write .agents/shousper-stories/config.json — the CLI owns the format.
Core principle: every answer becomes committed config; the gates you define here are what story done will enforce forever after. Get them runnable, not aspirational.
Preflight
- If
.agents/shousper-stories/config.jsonexists, this is reconfiguration — show the current config and confirm with your human partner before overwriting anything. - Confirm you are at the root of a git repository (
git rev-parse --show-toplevel). The board, worktrees, and locks are all repo-relative.
Interview
One topic at a time. Propose detected defaults; the human confirms or corrects.
1. Merge mode
| Mode | Who integrates | When to pick |
|---|---|---|
self |
The agent merges story/st-<id> into main when gates pass |
Solo, high trust, fastest iteration |
local |
Story parks in-review; human reviews the worktree and merges locally | Solo, human wants eyes on every change |
pr |
Push branch + GitHub PR; humans review/merge on GitHub | Teams ("multiplayer") |
If pr, probe before accepting the answer:
gh auth status # must be logged in
git remote get-url origin # must have a remote
gh repo view --json viewerPermission -q .viewerPermission # must be WRITE or ADMIN
Any probe fails → report exactly which one and what it said, and offer local as the fallback. Never configure pr mode on hope.
2. Gates
Detect the test runner from signature files and PROPOSE a test command gate:
| Signal | Proposed gate command |
|---|---|
bun.lock / bun.lockb |
bun test |
pnpm-lock.yaml |
pnpm test |
yarn.lock |
yarn test |
package-lock.json |
npm test |
Cargo.toml |
cargo test |
go.mod |
go test ./... |
pyproject.toml / pytest.ini |
pytest |
Justfile |
inspect just --list for test/check recipes |
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.
- 1mo ago Changed · -2 lines · +4 tokens per session scan B → A 9b0cfe317048
- 1mo ago First seen · 120 lines · 133 tokens per session scan B 8dd4aece3d45
setup is a skill published in the GitHub repository shousper/claude-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 1,550 once invoked, about $0.0005 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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,"…