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-configuration-as-codegit 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-configuration-as-code)<a href="https://agentmods.dev/skills/gatling/gatling-ai-extensions/gatling-configuration-as-code"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-configuration-as-code/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-configuration-as-code"><img src="https://agentmods.dev/badge/skills/gatling/gatling-ai-extensions/gatling-configuration-as-code.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.00059 | $0.00767 |
| Opus 5 | $0.00030 | $0.00383 |
| Sonnet 5 | $0.00012 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
gatling-configuration-as-code 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gatling - Configuration as Code
This skill provides guidance on how to generate or update the .gatling/package.conf package descriptor file for deploying tests to Gatling Enterprise.
Instructions
-
Discover simulations based on the project language and build tool used: Java with Maven, JavaScript/TypeScript with the JavaScript CLI, Kotlin with Gradle, and Scala with sbt. Collect their fully qualified class names (FQCN).
-
Read existing config: check if
.gatling/package.confalready exists. For reference checkassets/package.conffrom this skill using the Read tool. -
Before asking any questions, call all the proper MCP tools to get real data from the user's account:
- Which teams are available.
- Which managed and private locations are available.
- Check if a package already exists for this project.
- Check if a test (aka simulation) already exists for this project.
-
Ask the user what they need with the
AskUserQuestiontool. If a list has >4 items, output the full list as markdown in a text message and ask the user to specify their choice(s) by name.- Which tests to include.
- Package name (default to the project name, use artifactId if this is a Maven project).
- Team name or ID, asks the users if they want to create a new team.
- Load generator locations and weights, ask if they want to use a managed or private location.
- Any system properties or environment variables.
- Ramp up and ramp down time windows.
- Stop criteria.
-
Generate or update the file following the structure and rules below.
Key Rules
simulation(FQCN) is the only mandatory field per simulation entry.- Location
weightvalues must sum to 100 across all locations for a simulation. - System property names must be quoted (HOCON interprets dots as nested keys).
- Prefix system properties with
sensitive.to hide values from the dashboard. - Prefix environment variables with
SENSITIVE_to hide values from the dashboard. - The
defaultblock avoids repeating shared config; simulation-specific values override it. - Maps (
systemProperties,environmentVariables) are merged, with simulation values taking priority. ignoreDefaultsrefers to Gatling Enterprise's Default Load Generator Parameters, not thedefault {}block.- After first deploy, IDs are logged. Add them to
idfields for consistent updates (allows renaming without creating duplicates).
What ships with it
2 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 · 82 lines · 59 tokens per session scan A c3ab216b9b76
gatling-configuration-as-code is a skill published in the GitHub repository gatling/gatling-ai-extensions (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 767 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.