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 ash1794/vibe-engineering --skill scenario-matrixgit clone --depth 1 https://github.com/ash1794/vibe-engineeringWrote 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/ash1794/vibe-engineering/scenario-matrix)<a href="https://agentmods.dev/skills/ash1794/vibe-engineering/scenario-matrix"><img src="https://agentmods.dev/badge/skills/ash1794/vibe-engineering/scenario-matrix.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.00030 | $0.00628 |
| Opus 5 | $0.00015 | $0.00314 |
| Sonnet 5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
vibe-scenario-matrix 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- vibe-scenario-matrix — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-scenario-matrix
Test coverage isn't about code lines -- it's about user scenarios. Map them all.
When to Use This Skill
- Planning test coverage for a complex feature
- Preparing for a release or milestone review
- After expanding requirements significantly
- When stakeholders ask "what's tested?"
- Transitioning from ad-hoc testing to systematic testing
When NOT to Use This Skill
- Single-function unit testing (just write the test)
- Already have comprehensive test specifications
- Prototyping/spiking (too early for formal coverage)
Steps
-
Gather scenarios from:
- PRD / Requirements document
- User stories / acceptance criteria
- Bug reports (past failures = scenarios to test)
- User feedback / support tickets
- Edge cases discovered during development
-
Assign stable IDs -- Use format
[Section]-[Number]:- Example:
AUTH-001,PAYMENT-015,ONBOARD-003 - IDs never change once assigned (even if scenario text changes)
- Example:
-
Classify testing approach:
- Deterministic (61%): Can be tested with standard assertions
- LLM-as-Judge (24%): Needs qualitative assessment
- Simulation (11%): Needs multi-step environment
- Proxy Metric (4%): Can only be measured indirectly
-
Build the matrix:
| ID | Scenario | Expected Behavior | Test Approach | Status |
|---|---|---|---|---|
| AUTH-001 | User logs in with valid credentials | Redirect to dashboard, session created | Deterministic | PASS |
| AUTH-002 | User enters wrong password 5 times | Account locked for 30 minutes | Deterministic | NOT_IMPL |
| TONE-001 | System responds empathetically to frustration | Response acknowledges emotion without dismissing | LLM-as-Judge | PARTIAL |
- Track status: PASS / PARTIAL / FAIL / NOT_IMPLEMENTED / DEFERRED
Output Format
Scenario Acceptance Matrix: [Feature/Product]
Total Scenarios: X Coverage: Y% (PASS or PARTIAL)
| Status | Count | % |
|---|---|---|
| PASS | X | X% |
| PARTIAL | X | X% |
| NOT_IMPLEMENTED | X | X% |
| DEFERRED | X | X% |
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.
- 7d ago First seen · 78 lines · 30 tokens per session scan A d34b21534bc6
vibe-scenario-matrix is a skill published in the GitHub repository ash1794/vibe-engineering (10 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 628 once invoked, about $0.0002 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-31.
Other skills, from other repositories
verify
Runs this project's check chain through scripts/verify.py and reads the receipt it writes. Fires when tracked changes are finished, when the user asks whether work passes, before a commit, and before reporting a task done. Stays dormant in repositories with no detectable check chain, during read-only audits, and for…
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
create-test-plan
Analyze what changed and generate a structured test plan at .turbo/test-plans/ .md covering four escalating levels: basic functionality, complex operations, adversarial testing, and cross-cutting scenarios. Use when the user asks to "create a test plan", "plan tests", "what should I test", "generate test scenarios"…
feature-verify
Feature verification (READ-ONLY, P0-P5). Use when: verifying feature behavior after deployment, validating API responses, diagnosing production issues, post-deploy smoke test. Not for: modifying data (use feature-dev), code review (use codex-review-fast), writing tests (use codex-test-gen), security audit (use…
test-review
Test coverage review via Codex exec. Use when: reviewing test sufficiency, identifying coverage gaps, test quality audit. Not for: generating tests (use codex-test-gen), code review (use codex-code-review). Output: coverage analysis + gap report.
pre-pr-audit
Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (use…