Borrowing it
Nothing to install: this file belongs to eddiesanjuan/markupr. 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/eddiesanjuan/markupr/main/.claude/commands/audit.mdgit clone --depth 1 https://github.com/eddiesanjuan/markuprWrote 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/eddiesanjuan/markupr/audit)<a href="https://agentmods.dev/commands/eddiesanjuan/markupr/audit"><img src="https://agentmods.dev/badge/commands/eddiesanjuan/markupr/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.00000 | $0.00380 |
| Opus 5 | $0.00000 | $0.00190 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 7d 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.
What it actually says
Code Quality Audit
Perform a targeted code quality audit of the markupr codebase.
Instructions
-
Run all static analysis:
npm run lint npm run typecheckReport any errors or warnings.
-
Check for common issues in Electron apps:
- IPC channels defined in
src/shared/types.tsthat are unused or missing handlers nodeIntegrationorcontextIsolationmisconfigurations in window creation- Missing error boundaries in React components
- Unhandled promise rejections in main process code
- Memory leaks from event listeners not being cleaned up
- IPC channels defined in
-
Review security considerations:
- API keys should only be stored via keytar (never in plaintext config files)
- No
eval(),innerHTML, ordangerouslySetInnerHTMLwith user-supplied data - Preload script should not expose unnecessary APIs to the renderer
- Check
webPreferencesin BrowserWindow creation for safe defaults
-
Examine error handling patterns:
- Verify try/catch around ffmpeg operations (FrameExtractor)
- Verify try/catch around Whisper operations (WhisperService)
- Verify try/catch around Claude API calls (ClaudeAnalyzer)
- Check that errors surface user-friendly messages, not raw stack traces
-
Check for stale code:
- Unused imports or exports
- Dead code paths (unreachable conditions)
- TODO/FIXME/HACK comments that should be addressed
-
Provide a prioritized report:
- Critical -- security or data loss risks
- High -- bugs or broken functionality
- Medium -- code quality and maintainability
- Low -- style and cleanup opportunities
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.
- 7d ago First seen · 43 lines · 0 tokens per session scan A e83b7f0dd24f
audit is a command published in the GitHub repository eddiesanjuan/markupr (18 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 380 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
sdd-apply
Implement SDD tasks — writes code following specs and design.
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
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.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.