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 LambdaTest/agent-skills --skill api-versioning-helpergit clone --depth 1 https://github.com/LambdaTest/agent-skillsWrote 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/lambdatest/agent-skills/api-versioning-helper)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/api-versioning-helper"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-versioning-helper.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 77 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 89 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00138 | $0.01353 |
| Opus 5 | $0.00069 | $0.00677 |
| Sonnet 5 | $0.00028 | $0.00271 |
| Haiku 4.5 | $0.00014 | $0.00135 |
Grade A, and why
api-versioning-helper 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 8d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Versioning Skill
Design sustainable versioning strategies and manage API evolution without breaking clients.
Versioning Strategies Comparison
| Strategy | Example | Pros | Cons |
|---|---|---|---|
| URI versioning | /v1/users |
Simple, visible, cacheable | URL proliferation |
| Header versioning | API-Version: 2024-01 |
Clean URLs | Harder to test/share |
| Query param | /users?version=2 |
Easy to override | Pollutes query string |
| Accept header | Accept: application/vnd.api+json;v=2 |
REST-pure | Complex client setup |
| Date-based (Stripe) | Stripe-Version: 2023-10-16 |
Fine-grained, changelog-linked | Harder to communicate |
Recommendation: Use URI versioning (/v1/, /v2/) for public APIs. Use date-based for SDKs that pin a version.
Breaking vs Non-Breaking Changes
Non-breaking (safe to ship without version bump)
- Adding new optional fields to responses
- Adding new optional request fields
- Adding new endpoints
- Adding new enum values (if client ignores unknowns)
- Relaxing validation rules
- Bug fixes that align with documented behavior
Breaking (require new version)
- Removing fields from responses
- Renaming fields
- Changing field types (string → int)
- Making optional fields required
- Changing error codes or error shapes
- Removing endpoints
- Changing authentication method
- Adding required request fields
- Changing HTTP method for an endpoint
Versioning Lifecycle
v1 ACTIVE → v2 BETA → v2 GA → v1 DEPRECATED → v1 SUNSET
(6 months) (12 months) (6 month notice) (410 Gone)
Deprecation Response Header
Deprecation: true
Sunset: Sat, 01 Jan 2025 00:00:00 GMT
Link: <https://api.example.com/v2/users>; rel="successor-version"
Sunset Response (after deadline)
HTTP/1.1 410 Gone
Content-Type: application/json
{
"error": "version_sunset",
"message": "API v1 was sunset on 2025-01-01. Please migrate to v2.",
"migration_guide": "https://docs.example.com/migrations/v1-to-v2",
"v2_endpoint": "https://api.example.com/v2/users"
}
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.
- 8d ago First seen · 183 lines · 138 tokens per session scan A 24f0912c4927
api-versioning-helper is a skill published in the GitHub repository LambdaTest/agent-skills (367 stars, last pushed 1mo ago), licensed MIT. It adds 138 tokens to every session and 1,353 once invoked, about $0.0007 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-30.
Other skills, from other repositories
detecting-broken-object-property-level-authorization
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
flowforge-testing
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
kahea
Safely use HTTP APIs and finite WebSocket sessions through the Kāhea deterministic invocation kernel. Use when an agent must discover operations from OpenAPI, Postman, HAR, cURL, HTTP files, direct descriptors, websocket-session JSON/YAML, or the supported AsyncAPI 2.6/3.0 WebSocket subset; create and review sealed…
bruno
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize Bruno API Client, Bru markup language (.bru), CLI runner (@usebruno/cli), and CI/CD test pipelines.
api-spec-generator
Generate a ready-to-import Postman or Bruno collection from an API spec, Swagger/OpenAPI file, or endpoint description. Use this skill whenever the user wants to create, export, or scaffold an API test collection. Triggers on: "generate Postman collection", "create Bruno spec", "import-ready collection", "generate…