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 ivegamsft/basecoat --skill api-auditgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/api-audit)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/api-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/api-audit/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/ivegamsft/basecoat/api-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/api-audit.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.00070 | $0.00520 |
| Opus 5.5 | $0.00028 | $0.00208 |
| Sonnet 5.5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
api-audit 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Audit Skill
Comprehensive auditing of API designs, contracts, error handling strategies, versioning approaches, and integration patterns.
USE FOR
- Reviewing API endpoint definitions and route structures
- Validating request and response contracts (OpenAPI, schemas)
- Assessing HTTP status code usage and error handling patterns
- Evaluating API versioning strategies and deprecation practices
- Analyzing documentation completeness and accuracy
- Reviewing authentication and authorization patterns
- Assessing rate limiting, throttling, and quota strategies
- Evaluating consistency across API endpoints
- Identifying breaking changes and integration risks
- Creating structured audit findings with recommendations
DO NOT USE FOR
- Creating or revising API contracts, including design-focused contract reviews (use
api-design) - Implementing API endpoints or request handlers (use
backend-dev) - Writing other backend code
- Database schema design
- Frontend development or client implementation
- Infrastructure provisioning
- General code review (use
code-reviewskill)
Audit Checklist
- Endpoint Design: Naming conventions, HTTP verbs, parameter placement
- Contracts: Request/response schemas, type definitions, examples
- Error Handling: Status codes, error responses, failure scenarios
- Versioning: Strategy, deprecation policy, migration path
- Documentation: Completeness, accuracy, usability
- Security: Authentication, authorization, data protection
- Performance: Caching headers, pagination, filtering
- Consistency: Patterns, naming, response structure uniformity
- Integration: Backwards compatibility, changelog, client guidance
Related Skills
api-design— Designing API contracts and conducting design-focused contract reviewsbackend-dev— Implementing API endpoints, request handlers, and backend servicesbackend-audit— Reviewing backend implementation qualityapi-security— Security-focused API assessmentcontract-testing— Contract testing and verification
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.
- 1mo ago Changed · +2 lines 03e3143fd98c
- 1mo ago First seen · 57 lines · 70 tokens per session scan A 5ef4ed204d08
api-audit is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 520 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
platform-apex-generate
Primary Apex authoring skill for class generation, refactoring, and review. ALWAYS ACTIVATE when the user mentions Apex, .cls, triggers, or asks to create/refactor a class (service, selector, domain, batch, queueable, schedulable, invocable, DTO, utility, interface, abstract, exception, REST resource). Use this skill…
flow-next-impl-review
Carmack-level implementation review of changes via the configured backend. Use when asked to review code or a diff in a flow-next repo.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
api-contract-review
Use when auditing CloudBase cloud API wrappers, MCP tools, generated action metadata, or related docs for outdated or incorrect action names, parameters, casing, request shapes, or missing contract tests, especially during periodic quality review or before preparing corrective PRs.
ring:migrating-to-lib-observability
Migrating a Lerian Go app off lib-commons observability imports (deprecated shims or removed APIs) to lib-observability via a fixed mapping table, then bumps go.mod and validates the build; ring:backend-go applies the edits. Covers log/zap/runtime/assert, opentelemetry/tracing, HTTP middleware, context helpers, and…
ring:mapping-streaming-events
Mapping the eventable points in a Lerian Go service where lib-streaming should emit past-tense, durable, tenant-scoped business events, producing a PM-validated event catalog and instrumentation-map.json for ring:instrumenting-streaming-events. Three-pass discovery (Survey, Slice, Mark) with a scope fence and delivery…