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 skills add gatling/gatling-ai-extensions --skill gatling-bootstrap-projectgit clone --depth 1 https://github.com/gatling/gatling-ai-extensionsWrote 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/gatling/gatling-ai-extensions/gatling-bootstrap-project)<a href="https://agentmods.dev/skills/gatling/gatling-ai-extensions/gatling-bootstrap-project"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-bootstrap-project/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/gatling/gatling-ai-extensions/gatling-bootstrap-project"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-bootstrap-project.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.00021 | $0.00277 |
| Opus 5 | $0.00010 | $0.00138 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
gatling-bootstrap-project 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 11d 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
Bootstrap a Gatling project
Choose language
Ask user to choose one of the supported languages:
- Java
- Kotlin
- Scala
- TypeScript
- JavaScript
If user doesn't know, Java is a good default.
Choose a build tool
IF language is Java or Kotlin:
- Ask user to choose between Maven or Gradle. If user doesn't know, Maven is a good default.
IF language is Scala:
- Ask user to choose between sbt, Maven or Gradle.
IF language is TypeScript or JavaScript:
- Always use npm.
Set up the Gatling project
Once build tool and language are identified, read the corresponding file and follow its instructions:
- Maven: ./references/maven.md
- Gradle: ./references/gradle.md
- sbt: ./references/sbt.md
- npm: ./references/npm.md
Suggest next steps
- Explore the included sample simulation and check out the Gatling documentation linked in the README file.
- Run your first simulation locally.
- When ready to deploy to Gatling Enterprise, use the /gatling:gatling-build-tools skill for guidance.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 47 lines · 21 tokens per session scan A 7cb3a5e95190
gatling-bootstrap-project is a skill published in the GitHub repository gatling/gatling-ai-extensions (5 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 277 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-31.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
tool-abuse-detection
Detect tool misuse and unexpected code execution via dialogue testing. Use when the agent exposes file, code-execution, or network tools.
dev-browser
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website"…
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.