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 commands/pmdevsolutions/aurelius/verify-allgit clone --depth 1 https://github.com/PMDevSolutions/AureliusWrote 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/pmdevsolutions/aurelius/verify-all)<a href="https://agentmods.dev/commands/pmdevsolutions/aurelius/verify-all"><img src="https://agentmods.dev/badge/commands/pmdevsolutions/aurelius/verify-all.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.00708 |
| Opus 5 | $0.00000 | $0.00354 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
verify-all 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 today.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/verify-all — Run All Local Quality Checks
Runs every local quality check in sequence and reports a pass/fail summary. Wraps ./scripts/verify-all.sh so you do not have to remember each individual script.
Usage
/verify-all
/verify-all --skip dead-code,security
/verify-all --include lint-and-format,types,tests
Optional flags forward to the underlying script:
--skip <a,b,c>— skip named checks (comma-separated)--include <a,b>— run only the named checks--list— list available check names and exit
For machine-readable output and CI-style behavior, use /ci instead.
What runs
The orchestrator runs these checks in order. Each is independent — a failure in one does not stop the others.
| # | Check | Backing script | What it does |
|---|---|---|---|
| 1 | lint-and-format |
lint-and-format.sh --check |
ESLint + Prettier (no auto-fix) |
| 2 | types |
check-types.sh |
tsc --noEmit |
| 3 | tests |
run-tests.sh |
Vitest with coverage |
| 4 | accessibility |
check-accessibility.sh |
ESLint with jsx-a11y rules |
| 5 | tokens |
verify-tokens.sh |
Hardcoded-value scan vs lockfile |
| 6 | dead-code |
check-dead-code.sh |
Knip: unused exports/files/deps |
| 7 | security |
check-security.sh |
Dependency audit + anti-pattern scan |
| 8 | bundle-size |
check-bundle-size.sh |
Bundle analysis (skipped if no build artifact) |
Steps
1. Run the orchestrator
./scripts/verify-all.sh $ARGUMENTS
The script prints per-check progress and a summary table at the end:
=== Summary ===
Check Status Duration Reason
----- ------ -------- ------
lint-and-format pass 2618ms
types pass 1843ms
tests pass 4205ms
accessibility pass 1102ms
tokens pass 320ms
dead-code pass 2980ms
security pass 4111ms
bundle-size skip 0ms no build artifact (dist/.next/build/out)
Totals: 7 passed, 0 failed, 1 skipped
✓ All checks passed.
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.
- today First seen · 87 lines · 0 tokens per session scan A 9680e504834d
verify-all is a command published in the GitHub repository PMDevSolutions/Aurelius (8 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 708 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-09-04.
Other commands, from other repositories
figma-start
디자이너가 개발자의 원본 PR 위에서 검수를 시작할 때 호출하는 커맨드입니다. PR 링크 하나만 주면 프로젝트 클론부터 합니다 — 검수할 프로젝트를 미리 받아둘 필요가 없습니다. 브랜치 생성·체크아웃 후 빌드해서 기기에 올려 화면까지 띄워줍니다 — 실행할 기기·에뮬레이터가 없으면 검수에 맞는 걸 설치해서 만듭니다. 그 브랜치의 커밋 이력 패널도 개발툴에 띄워줍니다 — 지금까지 반영한 검수 내용을 검수 내내 옆에 두고 볼 수 있습니다. 커밋·푸시는 하지 않습니다. 디자이너가 화면을 먼저 확인한 뒤, 필요하면 /figma-apply로 피그마 변경을 반영합니다.
handoff
디자이너 작업 완료 신호 — design/ 브랜치로 dev 브랜치 타겟 PR을 만들고, 원본 dev PR 작성자를 리뷰어로 지정.
figma-apply
피그마 변경을 현재 design/ 브랜치에 반영(커밋·푸시). /figma-start 이후에 사용.
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
test
Generate comprehensive tests.