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/ngocsangyem/meowkit/auditgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/audit)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/audit"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/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 | $0.00000 | $0.00514 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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 4d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit — Full Security Audit
Usage
/audit [optional: specific directory or file]
Behavior
Runs a comprehensive security audit using mk:review (structural) + mk:cso (infrastructure) skills across all platforms detected in the project. Generates a security report.
Execution Steps
-
Detect platforms. Scan the project to identify which platforms/frameworks are in use (e.g., NestJS, Vue, Swift/iOS, Supabase, PostgreSQL).
-
Run
mk:csosecurity audit for each detected platform. Check for all blocked patterns defined inrules/security-rules.md:- Hardcoded secrets (API keys, passwords, tokens, JWT secrets in source)
anytype in TypeScript (should useunknown+ type guards)- SQL queries with string interpolation/template literals
- localStorage for auth tokens
- v-html with user-provided content
- UserDefaults for sensitive data (Swift)
- Row Level Security disabled or missing
- Controllers without auth guards (unless explicitly public and documented)
- process.env access without ConfigService wrapper (NestJS)
- anon key used in server-side context
- Disabled certificate validation (Swift)
- CASCADE DELETE without explicit approval
-
Classify findings by severity:
- PASS: No issues found in this area.
- WARN: Potential issue that should be reviewed but does not block shipping.
- BLOCK: Critical security issue that MUST be resolved before shipping. No exceptions.
-
Generate security report. Write to:
tasks/reviews/YYMMDD-security-report.mdReport includes: per-platform findings, severity per finding, file and line references, remediation guidance.
-
Print summary. Display findings grouped by severity:
🐱 Security Audit Results: BLOCK (2): [list] WARN (3): [list] PASS (8): [list]
Scope
- If a specific directory or file is provided, audit only that scope.
- If no scope is provided, audit the entire project.
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.
- 4d ago First seen · 60 lines · 0 tokens per session scan A 2ba715dcf870
audit is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 514 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.