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 jeremylongworth-source/AgentSkills --skill backend-test-plangit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/backend-test-plan)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/backend-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/backend-test-plan/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/jeremylongworth-source/agentskills/backend-test-plan"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/backend-test-plan.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.00050 | $0.00323 |
| Opus 5 | $0.00025 | $0.00161 |
| Sonnet 5 | $0.00010 | $0.00065 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
backend-test-plan 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.
What it actually says
Backend Test Plan
Core Workflow
- Identify changed behavior, risk areas, data stores, external integrations, auth boundaries, and production impact.
- Define coverage across unit, integration, contract, database/migration, authorization, error, performance, and regression tests.
- Specify fixtures, test data, mocks/fakes, environments, and cleanup needs.
- Tie each test to an acceptance criterion or failure mode.
- Include non-happy paths: denied access, invalid input, dependency failure, concurrency, retries, and rollback.
- Recommend what must pass before merge, release, or rollback.
Safety Rules
- Do not claim tests passed unless output is available.
- Do not use real production data or credentials in test plans.
- Escalate testing gaps for auth, payments, migrations, customer data, background jobs, and public APIs.
Deliverable Shape
For backend test plans, provide:
- Change and risk summary
- Test matrix
- Fixtures and environments
- Contract and integration coverage
- Data/migration coverage
- Auth and security coverage
- Performance or load checks when relevant
- Merge/release gates
References
- Read
references/backend-test-plan-checklist.mdwhen creating or reviewing backend test coverage.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 50 tokens per session scan A bcf1fd1fe273
backend-test-plan is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 6d ago), licensed MIT. It adds 50 tokens to every session and 323 once invoked, about $0.0003 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
dependency-injection
Use when writing or reviewing code with object graphs, service dependencies, or testability concerns. Covers constructor injection, DI containers, lifetimes, and anti-patterns (service locator, ambient context, over-injection).
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
convex-test
Generate convex-test tests for the app's Convex functions.
platform-apex-test-generate
Generate and validate Apex test classes with TestDataFactory patterns, bulk testing (251+ records), mocking strategies, assertion best practices, and disciplined test-fix loops. Use this skill when creating new Apex test classes, improving test coverage, debugging and fixing failing Apex tests, running test execution…