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 darellchua2/opencode-config-template --skill test-generator-framework-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/test-generator-framework-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/test-generator-framework-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/test-generator-framework-skill.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.00016 | $0.01993 |
| Opus 5 | $0.00008 | $0.00996 |
| Sonnet 5 | $0.00003 | $0.00399 |
| Haiku 4.5 | $0.00002 | $0.00199 |
Grade C, and why
test-generator-framework-skill scanned grade C 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
When protocol is enabled, this skill defaults to `Iterations: 10` (sufficient for typical single-pass workflows). Override with `Iterations: N` for specific tasks. Safety blocks: `.env`, `node_modules/`, `rm -rf`, `git p How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I provide a generic test generation framework for multiple languages:
- Analyze codebase to identify functions, classes, components
- Detect testing framework (Jest, Vitest, Pytest, etc.)
- Generate comprehensive test scenarios (happy paths, edge cases, errors)
- Create test files with proper structure
- Verify tests are executable
When to use me
Use when:
- Creating new test generation skill for specific language/framework
- Standardizing test generation across projects
- Building language-specific test generators
This is a framework skill - provides foundational workflow for other skills.
Steps
Step 1: Detect Framework and Package Manager
Framework detection:
- JavaScript/TypeScript:
grep -E "(jest|vitest)" package.json - Python:
grep pytest pyproject.tomlorrequirements.txt - Ruby:
grep -E "(rspec|minitest)" Gemfile - Go: Built-in testing
Package manager detection:
| Language | Manager | Lock File | Command |
|---|---|---|---|
| JS/TS | npm | package-lock.json |
npm run <script> |
| JS/TS | yarn | yarn.lock |
yarn <script> |
| JS/TS | pnpm | pnpm-lock.yaml |
pnpm run <script> |
| Python | Poetry | pyproject.toml |
poetry run <script> |
| Python | pip | requirements.txt |
Direct command |
Step 2: Analyze Source Code
Use glob patterns to find source files (exclude test files):
<glob_pattern> --exclude "**/*test*.<ext>" --exclude "**/test/**/*"
Identify:
- Functions, classes, modules, components
- Import statements and dependencies
- Export patterns
Step 3: Generate Test Scenarios
Scenario categories:
Happy path: Normal inputs, expected outputs, common use cases Edge cases: Empty inputs, boundary values (0, 1, -1, max, min), single-item collections Error handling: Invalid types, out of range values, missing params, invalid formats, permissions State management: Initial state, state updates, multiple transitions, reset, cleanup User interactions: Click events, form submissions, keyboard nav, input changes, hover/focus
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.
- 5d ago First seen · 232 lines · 16 tokens per session scan C a7205c450b62
test-generator-framework-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,993 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
credit-note-fixer
Fix the tiny credit-note formatting bug and rerun the exact targeted test command.
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
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"…
red-team-review
Unified adversarial review: v4.3 Strategic Matrix (MTA-004). 7-phase framework: Priors → Rubric → Adversarial Lenses → SWOT/TOWS → MCDA Decision Engine → Blind Spot/Kill Switch → Executive Summary. Absorbs: bias-detector.
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.
poc-validator
Proof-of-Concept (PoC) Validation Skill for security exploit verification. Use when validating exploitability of vulnerabilities, generating tailored payloads, executing exploits in sandboxed environments, or verifying successful exploitation (e.g., SQL injection, CVE exploitation, command injection). Triggers on…