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 irahardianto/awesome-agv --skill test-scenariosgit clone --depth 1 https://github.com/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/test-scenarios)<a href="https://agentmods.dev/skills/irahardianto/awesome-agv/test-scenarios"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/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/irahardianto/awesome-agv/test-scenarios"><img src="https://agentmods.dev/badge/skills/irahardianto/awesome-agv/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.00041 | $0.02171 |
| Opus 5.5 | $0.00016 | $0.00868 |
| Sonnet 5.5 | $0.00008 | $0.00434 |
| Haiku 4.5 | $0.00004 | $0.00217 |
Grade A, and why
test-scenarios 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 9d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Scenario Generator
Entry-point guard: This is a user-invoked command skill (
/test-scenarios). If you are a spawned subagent, do NOT execute this skill — return to your assigned scope card.
Purpose
Systematically derive test scenarios from requirements, code, or specifications. Uses a hybrid of structured derivation techniques and mutation-informed expansion to maximize coverage. Output feeds into the /test-unit, /test-integration, or /test-e2e skills after human review.
When to Use
- Starting testing on a new feature or module
- Comprehensive test planning before implementation
- Auditing test completeness on existing code
- Preparing test plans for QA handoff
When NOT to Use
- You already have scenarios and need to write tests — use
/test-unit,/test-integration, or/test-e2edirectly
Phases
Phase 1: INPUT
Objective: Establish the requirements source.
- Accept input from one or more sources:
- PRD / User Story — extract acceptance criteria, business rules
- API Specification — extract endpoints, schemas, error codes
- Existing Code — extract public API, business logic, state transitions
- UI Designs — extract user flows, validations, navigation paths
- Document the input source and scope boundaries
Gate: Input source identified and accessible.
Phase 2: INVENTORY
Objective: Map all existing test coverage across the codebase.
-
Crawl the codebase for existing tests:
- Unit tests: Find all test files (
*_test.*,*.spec.*,*.test.*). Extract test names/descriptions. Map to source modules. - Integration tests: Find all integration test files. Map to adapters/services under test.
- E2E tests: Find all E2E test files. Extract journey/scenario descriptions.
- Unit tests: Find all test files (
-
Produce Existing Coverage Inventory artifact as a structured table:
Unit Tests:
Module Test File Test Count Scenarios Covered discovered path count summary
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.
- 9d ago First seen · 205 lines · 41 tokens per session scan A 82e4d560e361
test-scenarios is a skill published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 41 tokens to every session and 2,171 once invoked, about $0.0002 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-10-15.
Other skills, from other repositories
om-module-scaffold
Build a complete standalone business app, module, or CRUD vertical slice using Open Mercato discovery, commands, APIs, ACL/setup, UI, events, search, migrations, and tests. Use for customer management, deal-pipeline changes, CRM lead capture, library/booking/rental systems, "create a module", "add CRUD entity"…
om-troubleshooter
Diagnose and fix standalone Open Mercato bugs across scope, commands, locking, fields, generated registries, UI hydration, cache/search, bootstraps, queues, and providers. Use for "fix bug", "why does this fail", "regression", "debug", "napraw błąd", or a failing test.
verify-bug
Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
common-subagent-driven-development
Execute multi-task implementation plans by dispatching a fresh implementer subagent per task with independent review gates. Use when implementing plans, executing multi-task PRs, or transitioning from planning to implementation.
implement-feature
Implement an approved feature plan with fresh-context slices, TDD, revision-bound evidence, and PR-ready output.