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/Fujigo-Software/f5-framework-claudeWrote 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/fujigo-software/f5-framework-claude/_test-shared)<a href="https://agentmods.dev/commands/fujigo-software/f5-framework-claude/_test-shared"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/_test-shared/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/fujigo-software/f5-framework-claude/_test-shared"><img src="https://agentmods.dev/badge/commands/fujigo-software/f5-framework-claude/_test-shared.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.00008 | $0.02217 |
| Opus 5.5 | $0.00003 | $0.00887 |
| Sonnet 5.5 | $0.00002 | $0.00443 |
| Haiku 4.5 | $0.00001 | $0.00222 |
Grade A, and why
_test-shared 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Shared Patterns
Internal Reference: This file contains shared patterns used by
/f5-test-*commands. Not directly invocable - Use/f5-test,/f5-test-unit,/f5-test-it,/f5-test-e2e, or/f5-tdd
STACK DETECTION MATRIX
Auto-Detection from .f5/config.json
BACKEND=$(jq -r '.stack.backend[0] // .stack.backend // "unknown"' .f5/config.json)
FRONTEND=$(jq -r '.stack.frontend // "unknown"' .f5/config.json)
Test Framework by Stack
| Stack | Test Framework | Coverage Tool | Config File |
|---|---|---|---|
| nestjs | Jest | istanbul | jest.config.js |
| spring | JUnit 5 + Mockito | JaCoCo | pom.xml |
| fastapi | pytest | pytest-cov | pytest.ini |
| go | go test | go cover | go.mod |
| django | pytest-django | coverage.py | pytest.ini |
| laravel | PHPUnit | phpunit | phpunit.xml |
| rails | RSpec | SimpleCov | .rspec |
| react | Vitest/Jest + RTL | c8/istanbul | vitest.config.ts |
| nextjs | Jest + RTL | istanbul | jest.config.js |
| vue | Vitest | c8 | vitest.config.ts |
| angular | Jasmine + Karma | istanbul | karma.conf.js |
| flutter | flutter_test | lcov | pubspec.yaml |
Test Commands by Stack
| Stack | Unit Test | Coverage | Watch |
|---|---|---|---|
| nestjs | npm test |
npm run test:cov |
npm run test:watch |
| spring | mvn test |
mvn jacoco:report |
- |
| fastapi | pytest |
pytest --cov |
pytest-watch |
| go | go test ./... |
go test -cover ./... |
- |
| react | npm test |
npm run test:coverage |
npm run test:watch |
| vue | npm test |
npm run test:coverage |
npm run test:watch |
MCP PRE-FLIGHT CHECK
Pattern for Commands Requiring MCP
## MCP Pre-Flight Check
| MCP Server | Required For | Status |
|------------|--------------|--------|
| Playwright | E2E, Visual, Browser tests | 🔄 Checking... |
| Sequential | Multi-step analysis, IT flows | 🔄 Checking... |
### If MCP Unavailable
**Degraded Mode Available:**
- ⚠️ `[MCP_NAME]` not available
- Continuing with limited functionality
- Some features disabled: [list features]
**To Enable Full Features:**
```bash
/f5-mcp status # Check MCP health
/f5-mcp profile full # Enable all MCPs
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 · 314 lines · 8 tokens per session scan A df47f311dd4a
_test-shared is a command published in the GitHub repository Fujigo-Software/f5-framework-claude (24 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 2,217 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-30.
Other commands, from other repositories
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
paul:verify
Guide manual user acceptance testing of recently built features.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
atdd
Start the ATDD workflow for a new feature. Optionally provide a feature description as an argument.
spec-check
Audit GWT acceptance test specs for implementation leakage. Optionally provide a specific file path.