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/lsampaioweb/ai-instructionsWrote 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/rules/lsampaioweb/ai-instructions/spring-boot-k6)<a href="https://agentmods.dev/rules/lsampaioweb/ai-instructions/spring-boot-k6"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-k6/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/rules/lsampaioweb/ai-instructions/spring-boot-k6"><img src="https://agentmods.dev/badge/rules/lsampaioweb/ai-instructions/spring-boot-k6.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.00000 | $0.00681 |
| Opus 5.5 | $0.00000 | $0.00272 |
| Sonnet 5.5 | $0.00000 | $0.00136 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
spring-boot-k6 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 14d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spring Boot k6 Contract
These rules apply when an application ships HTTP load or performance scripts. They do not apply to JUnit tests. Automated unit, slice, and context-load tests stay in the testing contract. Do not restate that contract here.
k6 is optional. Add these scripts only when the product needs load or performance checks.
When to add k6
- Add k6 when the product needs HTTP smoke, load, or authenticated-path performance checks against a running application.
- Do not add k6 to every greenfield app.
- Do not add a k6 Maven dependency.
- Do not run k6 from Maven Surefire or as a substitute for
mvn test.
Layout
- Put scripts in
src/test/k6/of the application module. - Use one script per scenario (for example smoke, staged load, or an authenticated path).
- Keep fixtures such as JSON payloads next to the scripts, not under
src/main.
Script contract
- Import
k6/httpand declareexport const optionswithvusplusduration, or withstages. - Call
check()on HTTP status, and on important body or header values when that is the point of the script. - Read the target from
__ENV.BASE_URL, defaulting tohttp://localhost:8080for local runs. - Prefer thresholds
http_req_failed: ['rate < 0.01']and a duration percentile. Set the duration limit to match the endpoint under test; do not copy a cookbook 200ms or 500ms number onto a deliberately slow path. - Do not invent request tags that the script never sets.
Secrets and authentication
- Load credentials from environment variables only. Never hardcode passwords or tokens in scripts.
- Send credentials with an
Authorizationheader. Never putuser:passin the URL. - When the API uses HTTP Basic (or a similar static header), build it once in
setup()and reuse it in the default function.
Reports
- Optional HTML summaries go under
src/test/k6/output/. - Add
src/test/k6/output/to.gitignorewhen the project writes k6 reports. - Never commit generated HTML reports.
- Never place k6 report HTML in
src/main/resources/templates/or other application static/UI paths.
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.
- 14d ago First seen · 75 lines · 0 tokens per session scan A d4576b777578
spring-boot-k6 is a cursor rule published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 681 tokens. 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-10-04.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.