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 ivanhoinacki/team-exp-claude-config --skill test-scenariosgit clone --depth 1 https://github.com/ivanhoinacki/team-exp-claude-configWrote 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/ivanhoinacki/team-exp-claude-config/test-scenarios)<a href="https://agentmods.dev/skills/ivanhoinacki/team-exp-claude-config/test-scenarios"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/test-scenarios/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/ivanhoinacki/team-exp-claude-config/test-scenarios"><img src="https://agentmods.dev/badge/skills/ivanhoinacki/team-exp-claude-config/test-scenarios.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.00132 | $0.03162 |
| Opus 5.5 | $0.00053 | $0.01265 |
| Sonnet 5.5 | $0.00026 | $0.00632 |
| Haiku 4.5 | $0.00013 | $0.00316 |
Grade A, and why
test-scenarios 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(git *), Bash(gh *), Bash(docker *), Bash(curl *), Bash(yarn *), Bash(npx *), Bash(node *), Bash(psql *), Read, Write, Edit, Grep, Glob, Agent How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Vault RAG (MANDATORY, BEFORE any Read/Grep)
You MUST call query_vault(query, service_filter) BEFORE reading codebase files or external sources. This is enforced by hook. No exceptions.
Test Scenarios -- Real Validation Before Commit
Validate that the feature works with real data, not just unit test mocks. Covers environment setup, test data seeding, automated tests, and manual smoke tests.
When to Use
After /code-review approves, before /commit. This is a quality gate.
/feature-dev -> /deslop -> /code-review -> /test-scenarios -> /commit -> /create-pr
Common Agent Mistakes
- Running tests without checking infra: Tests fail because Docker containers are down, not because code is wrong. Always verify environment first
- Testing only happy path: Missing edge cases, error paths, empty arrays, null values. Every scenario needs positive + negative + edge
- Assuming staging data matches expectations: Staging data changes daily. Always verify test data exists before running smoke tests
- Not asking user for VPN/tunnel: DB access and staging APIs require VPN. Always ask if VPN is connected before any remote operation
- Skipping test data setup: Running integration tests against empty tables. Seed or verify data exists first
- Running against empty local DB for provider features: When testing features that depend on real provider data (SSC/CMC sync, images, pickup points), the local DB is empty. ALWAYS ask user for VPN +
le aws login, then set up staging DB tunnel viale-tunnel.shand configure.envto point to the tunnel BEFORE starting the service. Without this, images won't load (Cloudinary IDs not in local DB) and synced data won't exist
Phase 1: Environment Verification
1.1 Local Infrastructure
# Check Docker containers
docker ps --format '{{.Names}}' | grep -E 'postgres|redis|nginx'
# Check which DB the service uses (from MEMORY.md Quick Configs)
# svc-experiences: PG16 :5439
# svc-ee-offer: PG14 :5436
# svc-order: PG (needs .env)
# svc-car-hire: Prisma
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.
- 2mo ago First seen · 385 lines · 132 tokens per session scan A f8fdbfbde1c6
test-scenarios is a skill published in the GitHub repository ivanhoinacki/team-exp-claude-config (2 stars, last pushed 26d ago), licensed MIT. It adds 132 tokens to every session and 3,162 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
session-rag-eval
Run and debug Chatbox session attachment RAG model evaluation with synthetic and real long-file fixtures.
dsh-error-handling
A workflow for designing and reviewing how software reports errors, partial success, unknown results, recovery, retries, cancellation, and failure feedback.