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/vilnacrm-org/php-service-template/testing-workflownpx skills add VilnaCRM-Org/php-service-template --skill testing-workflowgit clone --depth 1 https://github.com/VilnaCRM-Org/php-service-templateWhat 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.00016 | $0.00302 |
| Opus 5 | $0.00008 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
testing-workflow 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
Testing Workflow
Test Surfaces
make bats- Bash and Makefile behaviormake unit-tests- Unit suitemake integration-tests- Integration suitemake behat- BDD and end-to-end scenariosmake tests-with-coverage- PHPUnit with Clover outputmake infection- Mutation testing
Setup
For anything that touches database-backed behavior:
make setup-test-db
Practical Order
Small change
make unit-tests
Persistence or request-flow change
make setup-test-db
make unit-tests
make integration-tests
make behat
Risky refactor
make setup-test-db
make unit-tests
make integration-tests
make behat
make infection
Debugging Notes
- Re-run the smallest failing suite first.
- If only integration or Behat fails, confirm the database was recreated with
make setup-test-db. - When mutation testing fails, improve tests rather than relaxing Infection.
- If Makefile behavior is changed, run
make bats.
Done Criteria
- The changed behavior is covered by at least one relevant suite.
- The suite that failed has been rerun successfully.
- Any unrun suites are explicitly called out in the final summary.
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 · 64 lines · 16 tokens per session scan A 55c5037c272a
testing-workflow is a skill published in the GitHub repository VilnaCRM-Org/php-service-template (24 stars, last pushed 2mo ago), licensed CC0-1.0. It adds 16 tokens to every session and 302 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.