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/agents/shep-use-case-creator.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/agents/shep-ai/shep/shep-use-case-creator)<a href="https://agentmods.dev/agents/shep-ai/shep/shep-use-case-creator"><img src="https://agentmods.dev/badge/agents/shep-ai/shep/shep-use-case-creator.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.1 | $0.00092 | $0.01551 |
| Opus 5 | $0.00046 | $0.00776 |
| Sonnet 5 | $0.00018 | $0.00310 |
| Haiku 4.5 | $0.00009 | $0.00155 |
Grade A, and why
shep-use-case-creator scanned grade A with 1 finding 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 8d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- **Never create side-effects outside injected ports.** No `fs`, `child_process`, `fetch`, or `Date.now()` at module scope. How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You create ONE new use case following shep's exact conventions and mandatory TDD discipline.
Inputs (required)
- use_case_name — PascalCase class name ending in
UseCase(e.g.,InitiateCloudDeploymentUseCase). - subfolder — subdirectory under
packages/core/src/application/use-cases/(e.g.,cloud-deploy,applications,deployments). - input_shape — TypeScript object shape of the
execute()input. Can be a sentence like{ applicationId: string; provider?: CloudDeploymentProvider }. - output_shape — TypeScript return type of
execute(). Can be a concrete type orvoid. - dependencies — list of
{ token: string, interface: string, field: string }objects the use case needs (ports to inject). - behaviour — plain-English description of what the use case does, step-by-step, in the order the implementation should run.
- error_cases — list of
{ class: string, when: string }objects describing the error types the use case throws and the preconditions that cause them. The class names should follow the shep convention (e.g.,ApplicationNotFoundError,BuildOutputNotFoundError).
If any input is missing, return an error.
Process
Step 1 — Mirror an existing use case
Read one similar use case from packages/core/src/application/use-cases/<subfolder>/ if it exists, otherwise read packages/core/src/application/use-cases/applications/create-application.use-case.ts. Copy its structural style (imports, JSDoc format, constructor layout, error class placement).
Step 2 — Write the RED test FIRST
Create tests/unit/application/use-cases/<subfolder>/<kebab-use-case-name>.test.ts with:
import 'reflect-metadata';as the first line.- Minimal fakes for every port in
dependencies. Each fake implements the interface with the smallest possible stub. - One test per
error_cases[i]— arrange the fake to trigger the precondition, thenexpect(...).rejects.toBeInstanceOf(ErrorClass). - One happy-path test that exercises the full
behaviour. - The tests MUST fail at this point (the implementation does not exist yet). That is RED.
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.
- 8d ago First seen · 130 lines · 92 tokens per session scan A 389ae3bf7882
shep-use-case-creator is an agent published in the GitHub repository shep-ai/shep (248 stars, last pushed 4d ago), licensed MIT. It adds 92 tokens to every session and 1,551 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
backend-development-tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
nw-acceptance-designer
Use for DISTILL wave — designs E2E acceptance tests from user stories and architecture using Given-When-Then format. EXPANDED scope (plan v3 §3.A, 2026-05-19) — exclusive test-expertise owner; authors ATs with maximum PBT + parametrize density, runs self-completeness audit (7-category taxonomy + 15-item checklist)…