Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/VilnaCRM-Org/php-service-templatenpx agentmods add skills/vilnacrm-org/php-service-template/load-testingWrote 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/vilnacrm-org/php-service-template/load-testing)<a href="https://agentmods.dev/skills/vilnacrm-org/php-service-template/load-testing"><img src="https://agentmods.dev/badge/skills/vilnacrm-org/php-service-template/load-testing/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/vilnacrm-org/php-service-template/load-testing"><img src="https://agentmods.dev/badge/skills/vilnacrm-org/php-service-template/load-testing.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.00016 | $0.00233 |
| Opus 5.5 | $0.00006 | $0.00093 |
| Sonnet 5.5 | $0.00003 | $0.00047 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
load-testing 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 2mo 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
Load Testing
Use This Skill When
- adding a scenario under
tests/Load/scripts/ - changing load-test orchestration scripts
- debugging smoke, average, stress, or spike runs
Commands
make smoke-load-tests
make average-load-tests
make stress-load-tests
make spike-load-tests
make load-tests
make execute-load-tests-script scenario=<name>
./tests/Load/get-load-test-scenarios.sh
Rules
- Put K6 scenarios in
tests/Load/scripts/. - Keep scenario naming and config aligned with the existing shell wrappers.
- Prefer deterministic setup and teardown.
- Avoid hardcoded credentials or environment-specific values in committed test files.
Verification Path
- Start with
make smoke-load-tests. - Run the single changed scenario if applicable.
- Escalate to broader load commands only if needed.
Related Files
tests/Load/docker-compose.load_test.override.ymltests/Load/config.json.dist
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.
- 2mo ago First seen · 44 lines · 16 tokens per session scan A 817db17c8e06
load-testing is a skill published in the GitHub repository VilnaCRM-Org/php-service-template (25 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 16 tokens to every session and 233 once invoked, about $0.0001 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 skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.