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.
git clone --depth 1 https://github.com/iwritec0de/app-devWrote 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/commands/iwritec0de/app-dev/test)<a href="https://agentmods.dev/commands/iwritec0de/app-dev/test"><img src="https://agentmods.dev/badge/commands/iwritec0de/app-dev/test/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/commands/iwritec0de/app-dev/test"><img src="https://agentmods.dev/badge/commands/iwritec0de/app-dev/test.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.00006 | $0.00605 |
| Opus 5.5 | $0.00002 | $0.00242 |
| Sonnet 5.5 | $0.00001 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
test 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 1mo 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Test
Generate integration tests for API endpoints.
Load the js-testing skill for Vitest and React Testing Library patterns.
Usage
/test <route_or_resource> [--framework jest|vitest|pytest|gotest]
Arguments
Parse $ARGUMENTS to extract:
- route_or_resource (required) — Route path (
/api/users) or resource name (users) - --framework (optional) — Test framework. Auto-detected from project.
Instructions
1. Detect Test Framework
grep -q "vitest\|@vitest" package.json && echo "vitest"
grep -q '"jest"' package.json && echo "jest"
ls pytest.ini pyproject.toml 2>/dev/null && grep -q "pytest" pyproject.toml && echo "pytest"
ls *_test.go 2>/dev/null && echo "gotest"
Also detect:
- HTTP test client (
supertest,httpx,net/http/httptest) - Existing test patterns and conventions
2. Read the Endpoint
Find and read the route handler for the specified endpoint. Understand:
- Request schema (body, params, query)
- Response schema
- Auth requirements
- Error cases
- Side effects (database writes, external API calls)
3. Generate Tests
Create tests covering:
Happy Path:
- Valid request → expected response
- Correct status codes
- Response body matches schema
Validation:
- Missing required fields → 400
- Invalid types → 400
- Extra fields handled correctly
Authentication (if applicable):
- No token → 401
- Invalid token → 401
- Expired token → 401
- Insufficient permissions → 403
Not Found:
- Non-existent resource → 404
Edge Cases:
- Empty request body
- Very long strings
- Special characters in input
- Duplicate creation
- Concurrent modifications
Follow existing test patterns in the project. Match:
- File naming (
*.test.ts,*.spec.ts,*_test.go) - Setup/teardown patterns
- Mock/stub conventions
- Assertion style
4. Test File Location
Place tests following project convention:
- Co-located:
__tests__/resource.test.tsnext to route file - Separate:
tests/api/resource.test.ts - Go:
resource_test.goin same package
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.
- 1mo ago First seen · 94 lines · 6 tokens per session scan A 9ba63f284c3d
test is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 605 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:test-setup
Interactive Vitest setup wizard for Cloudflare Workers testing. Configures @cloudflare/vitest-pool-workers, mocks bindings, and creates example tests.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
better-auth:setup
Interactive setup wizard for better-auth authentication. Guides through database, framework, OAuth providers, and plugin configuration.
cloudflare-r2:presigned-url
Generate presigned URLs for secure client-side uploads or downloads.
ia-test-browser
Run browser tests on pages affected by current PR or branch.