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-build-toolsgit 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-build-tools)<a href="https://agentmods.dev/skills/gatling/gatling-ai-extensions/gatling-build-tools"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-build-tools/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-build-tools"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-build-tools.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.00051 | $0.00455 |
| Opus 5 | $0.00026 | $0.00228 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
gatling-build-tools 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 12d 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
Gatling Enterprise - Build Tools
Instructions
Step 1: Detect the build tool
Inspect the project root and identify the build tool by looking for these files, in this order:
- Maven:
pom.xml - JavaScript CLI:
package.json - Gradle:
build.gradle, orbuild.gradle.kts - sbt:
build.sbt
Step 2: Load build-tool-specific instructions
Once the build tool is identified, read the corresponding file and follow its instructions:
- Maven: ./references/maven-plugin.md
- JavaScript CLI: ./references/javascript-cli.md
- Gradle: ./references/gradle-plugin.md
- sbt: ./references/sbt-plugin.md
Step 3: Common pre-flight checks
These checks apply regardless of build tools:
- Verify
.gatling/package.confexists and is not empty. If missing or empty, help the user create it using the Configuration as Code skill. - Verify API token: check if
GATLING_ENTERPRISE_API_TOKENis set. - Verify tests referenced matches actual test classes in the source tree.
Step 4: Build-tool-specific steps
Follow the instructions from the file loaded in Step 2 for:
- Verifying the project compiles.
- Running the deploy command.
Step 5: Post-deploy
The output logs package and test IDs.
Suggest updating .gatling/package.conf with these IDs for consistent future deployments.
Step 6: Starting a test
Ask the user if they want to start the test on Gatling Enterprise. If so, follow the instructions from the file loaded in Step 2 for running the start command.
Troubleshooting
If the build tool deploy/start fails, see the /gatling:gatling-mcp skill's Troubleshooting section for authentication checks.
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.
- 12d ago First seen · 59 lines · 51 tokens per session scan A ad6331729835
gatling-build-tools is a skill published in the GitHub repository gatling/gatling-ai-extensions (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 455 once invoked, about $0.0003 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.