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 agentops-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/agentops-audit)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/agentops-audit"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/agentops-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.00063 | $0.00611 |
| Opus 5 | $0.00032 | $0.00305 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
agentops-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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Operations Audit Skill
Audit agent or skill specifications and produce an actionable scorecard, risk list, and revised spec.
USE FOR
- Scoring existing specs using a 0-5 rubric
- Finding ambiguity, safety gaps, and tool-policy issues
- Recommending concrete, prioritized fixes
- Producing a revised spec with measurable success criteria
- Generating routing rationale and estimated turn profile
- Auditing model IDs and reasoning-effort compatibility against the generated capability catalog
- Supporting
auditandcreate_and_auditflows inagent-designer
DO NOT USE FOR
- Writing product application code
- Infrastructure deployment and operations
- General-purpose code review outside agent/skill definitions
Required Scoring Dimensions (0-5)
claritysafety_compliancetool_correctnessambiguity_handlingcost_latency_fiteval_readiness
Audit Deliverables
scorecardrisksconcrete_fixesrevised_spec
Output Contract
Always include:
- Task-shaping classification (
execution_mode,estimated_turns,tool_profile,uncertainty) - Routing profile:
recommended_class:Fast | Balanced | Deep | Tool-Strictrationaleestimated_turns:1 | 2-3 | 4+risk_mitigations
- Artifacts:
audit_reportagent_specwhen a revised or regenerated spec is produced
Guardrails
- Do not assume model family names are portable across providers.
- Prefer measurable success criteria over subjective language.
- Escalate when constraints conflict (for example: fast + deep reasoning + lowest cost).
- Read
docs/reference/model-capabilities.jsonbefore recommending a model. - Treat
reasoning_depthas task metadata; do not emitreasoning_effortunless the selected model advertises configurable reasoning. - Report unknown model IDs and fixed-effort models separately. Effective organization and user entitlement remains a runtime check.
Related Skills
agent-design— authoring and scaffolding agent/skill assets
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 · 84 lines · 63 tokens per session scan A d47dc72f0898
agentops-audit is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 611 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-09-03.
Other skills, from other repositories
agent-builder
Design and build AI agents for any domain. Use when users: (1) ask to "create an agent", "build an assistant", or "design an AI system" (2) want to understand agent architecture, agentic patterns, or autonomous AI (3) need help with capabilities, subagents, planning, or skill mechanisms (4) ask about Claude Code…
code-review
Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
mcp-builder
Build MCP (Model Context Protocol) servers that give Claude new capabilities. Use when user wants to create an MCP server, add tools to Claude, or integrate external services.
Process PDF files - extract text, create PDFs, merge documents. Use when user asks to read PDF, create PDF, or work with PDF files.
crypto-arbitrage-bot-automated-trading
To orchestrate and deploy this execution skill dynamically via Autonomous AI Agent frameworks (LangChain, AutoGen, CrewAI), point your agent environment definition to the repository root and establish runtime parameters.
AgentPrecept
A project workflow for coordinating several coding agents on the same software project. It uses shared project structure, decisions, handoffs, checklists, and memory so agents can continue each other's work.