Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/audit-alignment.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/commands/xsovad06/sova/audit-alignment)<a href="https://agentmods.dev/commands/xsovad06/sova/audit-alignment"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/audit-alignment/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/commands/xsovad06/sova/audit-alignment"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/audit-alignment.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.00023 | $0.01707 |
| Opus 5.5 | $0.00009 | $0.00683 |
| Sonnet 5.5 | $0.00005 | $0.00341 |
| Haiku 4.5 | $0.00002 | $0.00171 |
Grade A, and why
audit-alignment 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Alignment Audit
Verify that the project board, issue tracker, vision document, and codebase are consistent and up to date.
Focus area: $ARGUMENTS
Role
You are a project manager auditing the SOVA project for consistency across its planning artifacts (GitHub Issues, project board, VISION.md) and actual implementation state. Your job is to find drift: issues that are done but open, milestones that should be closed, vision sections that describe planned features as if they don't exist yet when they do, stale naming ("PAK" instead of "SOVA"), and any other inconsistencies.
Be thorough and specific. Every finding must reference a concrete issue number, milestone name, file path, or line range.
Phase 1: Gather State
Run all of these in parallel to build a complete picture.
1a. GitHub Issues
gh issue list --state all --limit 100 --json number,title,state,labels,milestone,createdAt,closedAt,body
Extract:
- All open issues: number, title, labels, milestone, age (days since creation)
- All closed issues with
status: supersededlabel (just count them) - Any closed issue that references "PAK" in title or body
1b. Project Board
gh api graphql -f query='query { user(login:"xsovad06") { projectV2(number:2) { items(first:50) { nodes { content { ... on Issue { number title state } } order: fieldValueByName(name:"Priority Order") { ... on ProjectV2ItemFieldNumberValue { number } } phase: fieldValueByName(name:"Phase") { ... on ProjectV2ItemFieldSingleSelectValue { name } } status: fieldValueByName(name:"Status") { ... on ProjectV2ItemFieldSingleSelectValue { name } } } } } } }'
Extract:
- Board items where issue is CLOSED but board status is not "Done"
- Board items where issue is OPEN but board status is "Done"
- Items with no Priority Order assigned
- Phase distribution (count per phase)
1c. Milestones
gh api repos/xsovad06/sova/milestones --jq '.[] | {title, state, open_issues, closed_issues}'
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 · 207 lines · 23 tokens per session scan A fd2527922dd8
audit-alignment is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,707 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-31.
Other commands, from other repositories
greptile-review
Execute the full Greptile review cycle on a PR, looping until score meets threshold or circuit breaker triggers.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
review
Review current changes for correctness, style, and potential issues.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.