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/b1rdmania/ghostclaw/auditgit clone --depth 1 https://github.com/b1rdmania/ghostclawWhat 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 | $0.00000 | $0.05692 |
| Opus 5 | $0.00000 | $0.02846 |
| Sonnet 5 | $0.00000 | $0.01138 |
| Haiku 4.5 | $0.00000 | $0.00569 |
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 yesterday.
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 — 723 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Audit Command
Trigger: /design audit [file]
Purpose: Two-layer audit - first checks config violations against .design.json, then evaluates technical design quality against Impeccable principles.
Two-Layer Audit Approach
Layer 1: Config Compliance
Check against project's .design.json rules - are you following your own design system?
Layer 2: Technical Quality Check against Impeccable design principles (reference docs) - is your design system itself good?
Key Insight: You can be compliant with your config but still have poor design quality. Both layers matter.
Usage
/design audit src/components/Button.tsx # Audit single file
/design audit src/pages/HomePage.tsx # Audit page component
/design audit # Audit recent changes (interactive)
Detailed Process
Layer 1: Config Compliance Check
-
Load Project Config
# Read .design.json from project root # If missing, offer to run `/design init` first -
Parse Target File
- Extract all design-related code (CSS, Tailwind classes, inline styles, design tokens)
- Build list of all design values used
-
Check Each Category
Typography Compliance
- Font families: Must be from
typography.fontFamily - Font sizes: Must be from
typography.fontSize - Font weights: Must be from
typography.fontWeight - Flag: Any arbitrary values like
text-[17px]or custom font names
Color Compliance
- All colors: Must be from
colorsarray - Check: hex values, rgb/rgba, Tailwind classes
- Flag: Any hardcoded colors like
#3B82F6orrgb(255,0,0)
Spacing Compliance
- Margins, padding, gaps: Must be from
spacingscale - Flag: Arbitrary values like
mt-[13px]orpadding: 15px
Border Radius Compliance
- All radius values: Must be from
borderRadius - Flag: Custom values like
rounded-[12px]
Shadow Compliance
- All box-shadow usage: Must be from
shadows - Flag: Inline shadow definitions
- Font families: Must be from
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.
- yesterday First seen · 723 lines · 0 tokens per session scan A ec8825b2d625
audit is a command published in the GitHub repository b1rdmania/ghostclaw (91 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,692 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
triage-pr
Triage a PR — classify, optionally fix, optionally enable auto-merge.
tech-debt
Run bun run check:fix and then bunx knip and identify unused files and functions to refactor the project and simplify. Look at the deprecated features and confirm with the user to delete them. Look at the dependencies and remove the ones that are not needed based on knip results.
commit-and-pr
Let's commit the changes. Run tests, typechecks, and format checks. Then commit, push, and create a pull request.
story-short-scan
短篇网文扫榜。分析知乎盐言、番茄短篇等平台热门数据。.
audit_docs
Audit all project metadata files for stale counts, version mismatches, broken references, and missing entries. Reports discrepancies without auto-fixing.
tma1-peer
List recent sessions on this project by agent — peers (Codex, OpenClaw, Copilot CLI) or your own.