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 skills/floomhq/moto/deep-auditnpx skills add floomhq/moto --skill deep-auditgit clone --depth 1 https://github.com/floomhq/motoWrote 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/skills/floomhq/moto/deep-audit)<a href="https://agentmods.dev/skills/floomhq/moto/deep-audit"><img src="https://agentmods.dev/badge/skills/floomhq/moto/deep-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.00061 | $0.00939 |
| Opus 5 | $0.00030 | $0.00469 |
| Sonnet 5 | $0.00012 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
deep-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 6d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deep Audit Skill
Purpose
A systematic, thorough review of a codebase, system, or artifact. Not a quick scan - a deep investigation that surfaces issues a casual review would miss.
Step 1: Define audit scope
Clarify:
- What is being audited? (codebase, API, database, infrastructure, specific module)
- What type of audit? (security, performance, code quality, UX, all)
- What is the output? (prioritized issue list, report, PR with fixes)
Step 2: Gather context
# Understand the project structure
find . -type f -name "*.ts" | head -50
ls -la
# Read key files
cat CLAUDE.md README.md package.json
# Check recent changes
git log --oneline -20
# Check open issues
gh issue list --limit 20
Step 3: Run automated checks
Code quality
# TypeScript errors
npx tsc --noEmit
# Linting
npm run lint
# Test coverage
npm test -- --coverage
Security
# Check for known vulnerabilities
npm audit
# Check for hardcoded secrets
grep -r "password\|secret\|api_key\|token" --include="*.ts" --include="*.js" . | grep -v ".test." | grep -v "node_modules"
Dependencies
# Outdated packages
npm outdated
# Unused dependencies (if depcheck is available)
npx depcheck
Step 4: Manual review
Security checklist
- No secrets in code or git history
- Input validation on all user-controlled data
- SQL injection prevention (parameterized queries)
- XSS prevention (output escaping)
- Authentication on protected routes
- Authorization checks (can user access this resource?)
- Rate limiting on public endpoints
- Error messages don't expose internals
Code quality checklist
- No dead code (functions never called, variables never used)
- No duplicate logic (DRY violations)
- No magic numbers/strings (should be named constants)
- No TODO/FIXME comments without linked issues
- Error handling is consistent and not swallowed
- Logging is useful (not too verbose, not missing)
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.
- 6d ago First seen · 148 lines · 61 tokens per session scan A bd1f4ebb544f
deep-audit is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 939 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
performance
CLI performance optimization - startup time, memory usage, token savings benchmarking.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.