Borrowing it
Nothing to install: this file belongs to shep-ai/shep. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shep-ai/shep/main/.claude/skills/shep-kit-status/SKILL.mdgit clone --depth 1 https://github.com/shep-ai/shepWrote 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/shep-ai/shep/shep-kit-status)<a href="https://agentmods.dev/skills/shep-ai/shep/shep-kit-status"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/shep-kit-status/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/shep-ai/shep/shep-kit-status"><img src="https://agentmods.dev/badge/skills/shep-ai/shep/shep-kit-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.00746 |
| Opus 5 | $0.00039 | $0.00373 |
| Sonnet 5 | $0.00015 | $0.00149 |
| Haiku 4.5 | $0.00008 | $0.00075 |
Grade A, and why
shep-kit: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 10d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Status & Next Steps
Quickly orient the user on the current feature branch: what's done, what to try, and how to proceed.
Workflow
- Detect current branch —
git branch --show-current - Find the matching spec — look for a
specs/NNN-*directory whosefeature.yamlbranch field matches the current branch - Read these files (in parallel):
specs/NNN-*/feature.yaml— lifecycle, phase, progress, completed phasesspecs/NNN-*/tasks.yaml— task list with statesspecs/NNN-*/spec.yaml— summary, success criteria
- Read recent commits —
git log --oneline -10to see what was done - Produce the status report (see format below)
Output Format
Present a concise, user-friendly status report using this structure:
## [Feature Name] — Status
**Branch:** `feat/NNN-feature-name`
**Phase:** <current phase from feature.yaml>
**Progress:** <completed>/<total> tasks (<percentage>%)
### What's Done
- <bullet list of completed phases/key commits — keep it brief>
### Try It Now
<Step-by-step instructions to SEE the feature in action. Be specific:>
1. **Build:** `pnpm build`
2. **CLI:** `shep settings model` → pick a model
3. **CLI:** `shep feat new --model claude-opus-4-6 "test feature"`
4. **Web UI:** `pnpm dev:web` → open http://localhost:3000 → Settings → Model picker
5. **Tests:** `pnpm test` → all green
<Tailor these steps to the actual feature. Reference specific commands, URLs, UI paths, clicks.>
### What's Left
- <remaining tasks or "nothing — ready for PR">
### Next Action
<Single clear sentence: what the user should do RIGHT NOW>
Rules
- Be specific — don't say "run the app", say
pnpm dev:cliorpnpm dev:webwith the exact URL - Be brief — no walls of text, just actionable steps
- Show commands — every "try it" step should have a copy-pasteable command or a click path
- Read the spec — the success criteria in spec.yaml tell you what the user should be able to verify
- Check task states — if tasks.yaml shows all tasks as Todo but commits exist, the feature was implemented outside the task tracker (common). Use commits + build status as ground truth.
- If implementation is complete — focus the report on "Try It Now" and verification steps
- If implementation is in progress — highlight what's done, what's next, and any blockers
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.
- 10d ago First seen · 67 lines · 77 tokens per session scan A 3bc5172420e1
shep-kit:status is a skill published in the GitHub repository shep-ai/shep (248 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 746 once invoked, about $0.0004 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-30.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…