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 agentmods add skills/rakovi4/continue-framework/test-allnpx skills add rakovi4/continue-framework --skill test-allgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWhat 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 | $0.00035 | $0.00327 |
| Opus 5 | $0.00017 | $0.00163 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
test-all 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 2d 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
Run All Tests
Runs the complete test suite: unit tests in parallel, then acceptance tests.
Setup
Read ProductSpecification/technology.md Conventions table for:
- Backend test command pattern (with module substitution)
- Frontend test command
- Acceptance test command
Discover backend adapter modules by listing directories under backend/adapters/.
Workflow
Phase 1: Run Unit Tests in Parallel
Run ALL of these commands concurrently using multiple shell calls started before awaiting any result:
- Backend usecase tests:
{Backend test command}with module = usecase - Backend adapter tests: one
{Backend test command}per adapter module discovered - Frontend tests:
{Frontend test command}
Wait for all to complete. If any fail, report failures and STOP.
Phase 2: Start Backend
Execute the named run-backend skill and await startup.
Wait for backend to start.
Phase 3: Run Acceptance Tests
{Acceptance test command} for backend tests
Phase 4: Stop Backend
Execute the named stop-backend skill and await completion.
Output
Report summary:
- Backend unit tests: PASS/FAIL (usecase + each adapter)
- Frontend unit tests: PASS/FAIL
- Acceptance tests: PASS/FAIL (with details if failed)
- Overall: PASS/FAIL
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.
- 2d ago First seen · 54 lines · 35 tokens per session scan A 94f240af4c4d
test-all is a skill published in the GitHub repository rakovi4/continue-framework (50 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 327 once invoked, about $0.0002 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-30.
Other skills, from other repositories
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies.
testing
Writing or debugging tests, choosing unit vs integration style, Postgres/ClickHouse tests, regenerating ClickHouse test schema, or exporting test helpers from packages without pulling test code into production bundles.
detect-flaky-tests
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM lanes). For each newly-detected flaky test or infra issue, opens a GitHub issue with full evidence and a draft fix PR. Does…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
test-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
test
Run tests. Use after code changes to validate. Arguments: unit (default, no GPU), e2e (with models), filter name, or all.