Borrowing it
Nothing to install: this file belongs to victoriacity/openakari. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/victoriacity/openakari/main/.claude/skills/self-audit/SKILL.mdgit clone --depth 1 https://github.com/victoriacity/openakariWrote 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/victoriacity/openakari/self-audit)<a href="https://agentmods.dev/skills/victoriacity/openakari/self-audit"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/self-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/victoriacity/openakari/self-audit"><img src="https://agentmods.dev/badge/skills/victoriacity/openakari/self-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.00030 | $0.01805 |
| Opus 5.5 | $0.00012 | $0.00722 |
| Sonnet 5.5 | $0.00006 | $0.00361 |
| Haiku 4.5 | $0.00003 | $0.00180 |
Grade A, and why
self-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 2mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/self-audit [time-range]
Audit recent session work for compliance with CLAUDE.md conventions. The argument specifies the scope: last-session (default), 24h, 3d, or 7d. Reads recent commits and diffs to identify convention violations.
When to use this vs alternatives
- Use
/self-auditwhen you want to check whether recent sessions followed CLAUDE.md conventions (log entries, commit discipline, experiment structure, task tags). Works on committed history. - Use
pixi run validatewhen you want to check experiment YAML frontmatter and structural validity. Validate checks schema; self-audit checks behavioral conventions. - Use
/reviewwhen you want to check whether specific findings are valid or metric computations are meaningful./reviewchecks claim quality and methodology;/self-auditchecks process compliance and workflow adherence.
Scope
This skill checks conventions that are NOT already enforced by code:
| Convention | Enforced by code? | Self-audit checks? |
|---|---|---|
| EXPERIMENT.md frontmatter schema | Yes (pixi run validate) |
No — defer to validator |
| Session footer presence | Yes (verify.ts) |
No — defer to verifier |
| Orphaned files | Yes (verify.ts, auto-commit.ts) |
No — defer to verifier |
| Log entry per session | Partially (verify.ts checks modified READMEs) |
Yes — deeper check |
| Inline logging (discovery → file) | No | Yes |
| Cross-referencing (log entries → experiment dirs) | No | Yes |
| Findings provenance (script or arithmetic) | Yes (verify.ts) |
No — defer to verifier |
Task lifecycle tags ([in-progress] cleared) |
Yes (verify.ts) |
No — defer to verifier |
| Decision debt (implicit choices) | No | Yes |
| Budget check before resource work | No | Yes |
| Experiment record created for non-trivial work | No | Yes |
| Archive threshold (README log >5 entries) | No | Yes |
| Partial completion anti-pattern | No | Yes |
Procedure
1. Determine scope
Parse the time-range argument:
last-session(default): examine the most recent session's commits only24h,3d,7d: examine all commits in that time window
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.
- 2mo ago First seen · 171 lines · 30 tokens per session scan A 96efac264231
self-audit is a skill published in the GitHub repository victoriacity/openakari (47 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 1,805 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.