Borrowing it
Nothing to install: this file belongs to jayminwest/kotadb. 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/jayminwest/kotadb/develop/.claude/commands/issues/audit.mdgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/audit)<a href="https://agentmods.dev/commands/jayminwest/kotadb/audit"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/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/commands/jayminwest/kotadb/audit"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/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.00000 | $0.02882 |
| Opus 5.5 | $0.00000 | $0.01153 |
| Sonnet 5.5 | $0.00000 | $0.00576 |
| Haiku 4.5 | $0.00000 | $0.00288 |
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 1mo 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 — 280 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit and Close Stale GitHub Issues
Template Category: Structured Data
Systematically audit open GitHub issues to identify candidates for closure. This command helps maintain a clean issue tracker by finding completed, obsolete, or duplicate issues that can be safely closed.
Steps
-
Sync repo state
git fetch --all --prunegit pull --rebase(ensure you have latest commits and PRs)
-
Fetch all open issues
gh issue list --limit 100 --state open --json number,title,labels,body,createdAt,updatedAt,comments- Include all issues regardless of age (we'll filter in analysis)
- Capture full issue metadata for audit trail
-
Check blocked issues for unblocking opportunities
Before identifying closure candidates, audit issues with
blockedlabel:- Fetch all blocked issues:
gh issue list --label blocked --state open --json number,title,labels,body - For each blocked issue, parse the "Depends On" relationships from issue body
- Check if blocking issues are now closed/merged:
gh issue view <blocking-number> --json state - If all blocking issues are resolved:
- Remove
blockedlabel:gh issue edit <number> --remove-label blocked - Add comment explaining unblock:
gh issue comment <number> --body "Unblocked: all dependencies resolved (closes #X, #Y)" - Update issue body to remove or strikethrough "Depends On" references
- Remove
- If some blockers remain, add comment with current blocker status
- Track unblocked issues for prioritization report
- Fetch all blocked issues:
-
Identify closure candidates
Category 1: Completed but not closed
- Check for issues with related PRs that merged:
gh pr list --state merged --search "fixes #<number>" - Look for commit messages mentioning issue numbers:
git log --all --grep="#<number>" --oneline - Verify issue acceptance criteria are met by reviewing merged code
- Closure reason: "Completed via PR #X"
Category 2: Obsolete or superseded
- Check for "Supersedes" relationships in issue metadata
- Identify issues made obsolete by architectural changes (check recent merged PRs)
- Look for issues referencing removed dependencies or deprecated features
- Review git history for major refactors that resolved the issue implicitly
- Closure reason: "Superseded by #X" or "Obsolete after PR #Y"
- Check for issues with related PRs that merged:
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.
- 1mo ago First seen · 280 lines · 0 tokens per session scan A d546abb76da6
audit is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,882 tokens. 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 commands, from other repositories
auto-sprint
Orchestrateur de sprint de bout en bout (démarrage -> décomposition -> validation -> implémentation -> PR -> CI -> revue -> rétro -> merge).
review
Préparation Sprint Review.
bootstrap
Grupo: Framework DT En una frase: Usar El DT como base: promover al raíz y soltar el remoto del template. Cuándo: Arrancar un proyecto nuevo a partir del template. Quién: Cualquier operador del repo.
sync-todos-to-github
Convert TodoWrite task list to GitHub plan issue (triggers automation).
ready-pr-in-review
Move a PR from Draft to Ready for Review, assign a reviewer, add labels, and sync the related Jira ticket to In Review with the correct assignee.
wrapup
Draft PR + lessons + vault updates + git checklist. Phase 5.