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-compliancegit 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-compliance)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/api-compliance"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/api-compliance.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Tool Misuse · line 39 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00167 | $0.01779 |
| Opus 5 | $0.00084 | $0.00890 |
| Sonnet 5 | $0.00033 | $0.00356 |
| Haiku 4.5 | $0.00017 | $0.00178 |
Grade A, and why
api-compliance-checker 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Compliance & Audit Skill
Design compliant API patterns for GDPR, PCI-DSS, HIPAA, SOC2, and other regulatory frameworks.
GDPR Data Subject Rights Endpoints
POST /api/v1/privacy/data-export-request — user requests copy of their data (Art. 20)
GET /api/v1/privacy/data-export/{token} — download export (after processing)
POST /api/v1/privacy/deletion-request — right to erasure (Art. 17)
GET /api/v1/privacy/deletion-status/{id} — track deletion progress
POST /api/v1/privacy/rectification — correct inaccurate personal data (Art. 16)
GET /api/v1/privacy/consent — get user's consent records
POST /api/v1/privacy/consent — record/update consent
DELETE /api/v1/privacy/consent/{purpose} — withdraw consent for a purpose
POST /api/v1/privacy/portability — export data in machine-readable format
Data Export Response
{
"request_id": "uuid",
"status": "processing",
"estimated_completion": "2024-01-02T00:00:00Z",
"download_url": null,
"expires_at": null
}
Consent Record
{
"user_id": "uuid",
"consents": [
{
"purpose": "marketing_email",
"granted": true,
"granted_at": "2023-06-01T00:00:00Z",
"ip_address": "1.2.3.x",
"method": "explicit_checkbox"
},
{
"purpose": "analytics",
"granted": false,
"withdrawn_at": "2023-12-01T00:00:00Z"
}
]
}
PCI-DSS Field Masking Rules
| Field | Storage | API Response | Logs |
|---|---|---|---|
| Card number (PAN) | Tokenised only | **** **** **** 4242 |
Never log |
| CVV/CVC | Never store | Never return | Never log |
| Expiry date | Encrypted | MM/YY only |
Never log |
| Cardholder name | Encrypted | Masked A*** S*** |
Never log |
| Bank account number | Tokenised | Last 4 digits only | Never log |
{
"payment_method": {
"type": "card",
"last4": "4242",
"brand": "visa",
"exp_month": 12,
"exp_year": 2027,
"token": "tok_abc123"
}
}
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 · 231 lines · 167 tokens per session scan A 6faae6a21a0d
api-compliance-checker is a skill published in the GitHub repository LambdaTest/agent-skills (367 stars, last pushed 1mo ago), licensed MIT. It adds 167 tokens to every session and 1,779 once invoked, about $0.0008 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
jsonapi
Strict JSON:API v1.1 specification compliance. Trigger: When creating or modifying API endpoints, reviewing API responses, or validating JSON:API compliance.
validating-us-core
Validate FHIR R4 resources and Bundles against US Core / USCDI profiles with the official HL7 FHIR validator before submitting to an EHR. Covers running validatorcli.jar (or the public validator.fhir.org), declaring meta.profile, must-support elements, common conformance gaps (missing code/category/status), and…
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.
telnyx-10dlc-curl
10DLC brand and campaign registration for US A2P messaging compliance. Assign phone numbers to campaigns.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
806-regulations-eu-data-act
Use when reviewing, designing, or modifying Java enterprise systems that expose, exchange, store, process, export, or port data across users, businesses, connected products, cloud providers, APIs, event streams, AI data pipelines, data spaces, or SaaS platforms and need EU Data Act engineering controls. This should…