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 backend-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/backend-audit)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/backend-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/backend-audit.svg" alt="Measured on agentmods" 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.00082 | $0.00507 |
| Opus 5 | $0.00041 | $0.00253 |
| Sonnet 5 | $0.00016 | $0.00101 |
| Haiku 4.5 | $0.00008 | $0.00051 |
Grade A, and why
backend-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 3d 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
Backend Audit Skill
Comprehensive auditing of backend implementations, including code quality, testing coverage, performance characteristics, security practices, and maintainability.
USE FOR
- Reviewing backend service implementations for code quality
- Assessing test coverage and test strategy effectiveness
- Identifying performance bottlenecks and optimization opportunities
- Detecting security vulnerabilities and insecure patterns
- Evaluating code organization, maintainability, and technical debt
- Analyzing logging, error handling, and observability
- Reviewing database interaction patterns and query performance
- Assessing dependency health and supply chain risk
- Creating structured audit findings with severity ratings
DO NOT USE FOR
- Writing backend code from scratch (use
backend-devskill) - Designing database schemas (use related schema skills)
- API contract design (use
api-designskill) - Frontend code review (use appropriate frontend skills)
- Infrastructure provisioning (use
infrastructure-auditskill) - General code reviews (use
code-reviewskill)
Audit Checklist
- Code Quality: Complexity, duplication, naming, structure
- Testing: Unit, integration, e2e coverage; test quality and maintainability
- Security: Input validation, authentication, authorization, secrets management
- Performance: Query efficiency, caching, connection pooling, async patterns
- Error Handling: Exception handling, logging, graceful degradation
- Dependencies: Versions, vulnerabilities, necessity, supply chain
- Observability: Logging, tracing, metrics, debugging capability
- Maintainability: Documentation, comments, architectural clarity
Related Skills
code-review— General code review for bugs and regressionsapi-audit— API endpoint and contract auditingbackend-dev— Backend development and implementationsecurity— Security vulnerability assessment
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.
- 3d ago First seen · 55 lines · 82 tokens per session scan A c95a08fb0bca
backend-audit is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 507 once invoked, about $0.0004 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-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.
principle-model-the-domain
Apply when writing stateful logic, or when code branches a lot or repeats a shape assumption across files. Encode the domain in a structure instead of scattered conditionals.
code-review-nodejs
Applies Node.js-specific code review patterns for async I/O, streams, security, process management, and dependency hygiene. Use when reviewing Node.js server code, route handlers, middleware, or any JavaScript file alongside package.json without TypeScript. Triggers on sync I/O in request paths, missing stream…