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 agentmods add skills/synaptiai/agent-capability-standard/auditnpx skills add synaptiai/agent-capability-standard --skill auditgit clone --depth 1 https://github.com/synaptiai/agent-capability-standardWrote 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/synaptiai/agent-capability-standard/audit)<a href="https://agentmods.dev/skills/synaptiai/agent-capability-standard/audit"><img src="https://agentmods.dev/badge/skills/synaptiai/agent-capability-standard/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 | $0.00034 | $0.02730 |
| Opus 5 | $0.00017 | $0.01365 |
| Sonnet 5 | $0.00007 | $0.00546 |
| Haiku 4.5 | $0.00003 | $0.00273 |
Grade A, and why
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 4d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Live Context
Current audit context:
- Recent git commits: !
git log --oneline -10 2>/dev/null || echo "No git history" - Git authors today: !
git log --since="midnight" --format="%an" 2>/dev/null | sort | uniq -c || echo "None" - Uncommitted changes: !
git status --short 2>/dev/null || echo "Not a git repo" - Recent file modifications: !
find . -type f -mtime -1 -not -path './.git/*' 2>/dev/null | wc -l | tr -d ' 'files in last 24h - Audit log exists: !
ls -la .audit/ 2>/dev/null | head -5 || echo "No .audit/ directory" - Checkpoint log exists: !
ls -la .checkpoints/ 2>/dev/null | head -5 || echo "No .checkpoints/ directory"
Intent
Execute audit to create a structured record of actions taken, tools invoked, changes made, and the reasoning behind decisions. This provides accountability, enables investigation of issues, and supports compliance requirements.
Success criteria:
- Complete chronological record of relevant actions
- Every action linked to actor, timestamp, and rationale
- Changes documented with before/after state
- Provenance chain for all outputs
Compatible schemas:
schemas/output_schema.yaml
Inputs
| Parameter | Required | Type | Description |
|---|---|---|---|
scope |
Yes | string|array | What to audit: file paths, action types, or "session" for all |
time_window |
No | object | Start/end timestamps to bound the audit |
actor |
No | string | Filter by specific actor (agent, user, tool) |
detail_level |
No | enum | summary, standard, verbose (default: standard) |
include_diffs |
No | boolean | Whether to include actual change diffs (default: false) |
Procedure
-
Define audit scope: Determine what to include in the audit
- Parse scope parameter to identify targets
- Apply time_window filter if provided
- Identify relevant log sources (git log, tool invocations, file changes)
-
Collect action records: Gather all actions within scope
- Read git log for commits and their messages
- Review tool invocation history if available
- Identify file changes (created, modified, deleted)
- Record timestamps for each action
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.
- 4d ago First seen · 311 lines · 34 tokens per session scan A 006a801fa566
audit is a skill published in the GitHub repository synaptiai/agent-capability-standard (4 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,730 once invoked, about $0.0002 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-31.
Other skills, from other repositories
researchers-legal
Researches court documents, indictments, plea agreements, and sentencing records. Use when the album subject involves legal proceedings or criminal cases.
plagiarism-checker
Scans lyrics for phrases that may match existing songs using web search and LLM knowledge. Use before release to check for unintentional borrowing.
prior-art-search
Systematic 7-step methodology for comprehensive patent prior art searches and patentability assessments using BigQuery and CPC classification.
bigquery-patent-search
Fast, cloud-based patent searching across 100 million+ worldwide patents using Google BigQuery - keyword search, CPC classification, patent details retrieval.
sbom-generate
Usar para generar Software Bill of Materials para cumplimiento del CRA. También: Software Bill of Materials, inventario de componentes, CycloneDX, SPDX, cadena de suministro.
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.