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 batterfried-philosophy172/Agent-Startup-Skills --skill test-engineergit clone --depth 1 https://github.com/batterfried-philosophy172/Agent-Startup-SkillsWrote 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/batterfried-philosophy172/agent-startup-skills/test-engineer)<a href="https://agentmods.dev/skills/batterfried-philosophy172/agent-startup-skills/test-engineer"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/test-engineer/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/batterfried-philosophy172/agent-startup-skills/test-engineer"><img src="https://agentmods.dev/badge/skills/batterfried-philosophy172/agent-startup-skills/test-engineer.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.00049 | $0.00463 |
| Opus 5 | $0.00024 | $0.00231 |
| Sonnet 5 | $0.00010 | $0.00093 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
test-engineer 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 10d 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.
This is a copy
100% identical to test-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Test Engineer — Quality Assurance Agent
Purpose
Ensure the codebase works correctly by writing automated tests and identifying edge cases that the Coder may have missed.
When to Use
- After the codebase is implemented
- When the user asks for test coverage
- Before security audit (Phase 7 of SaaS Accelerator)
Process
Step 1: Test Strategy
Define what to test:
- Unit Tests: Individual functions and utilities
- Integration Tests: API endpoints (request → response)
- Edge Cases: Empty inputs, boundary values, unauthorized access
Step 2: Unit Tests
For each business logic function:
- Test the happy path (expected inputs → expected outputs)
- Test with invalid inputs (null, empty, wrong type)
- Test boundary values (min/max limits)
Step 3: API Integration Tests
For each API endpoint:
- Test successful request (correct status code and response body)
- Test with missing required fields (expect 400)
- Test without authentication on protected routes (expect 401)
- Test with invalid data types (expect 422)
Step 4: Edge Case Identification
Systematically check:
- What happens with an empty database?
- What happens with duplicate entries?
- What happens with very long strings?
- What happens with concurrent requests?
- What happens when an external service is unavailable?
Step 5: Test Runner Configuration
Generate the test runner config file (e.g., jest.config.js, pytest.ini)
and a test run command in package.json scripts.
Output
- Test files organized in a
tests/directory testing_plan.mdwith coverage summary- Manual test checklist for things that cannot be automated
Exit Criteria
- Every API endpoint has at least one happy-path test
- Every core business logic function has unit tests
- At least 5 edge cases are explicitly tested
- Test runner is configured and documented
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.
- 10d ago First seen · 65 lines · 49 tokens per session scan A a225c549b6a8
test-engineer is a skill published in the GitHub repository batterfried-philosophy172/Agent-Startup-Skills (2 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 463 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-engineer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
solution-validation-testing
When the user wants to verify optimization code: independent feasibility checkers, objective recomputation separate from the solver, unit tests for constraint builders and operators, known-optimum regression tests, and exact-vs-heuristic cross-validation on small instances. Also use when the user mentions "validate…
phx-verify
Verify Elixir/Phoenix changes — compile, format, and test in one loop. Use after implementation, before PRs, or after fixing bugs.
testing-r-packages
Best practices for writing R package tests using testthat version 3+. Use when writing, organizing, or improving tests for R packages. Covers test structure, expectations, fixtures, snapshots, mocking, and modern testthat 3 patterns including self-sufficient tests, proper cleanup with withr, and snapshot testing.
phx-work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after phx-plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.