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.
git clone --depth 1 https://github.com/iwritec0de/app-devWrote 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/iwritec0de/app-dev/audit)<a href="https://agentmods.dev/commands/iwritec0de/app-dev/audit"><img src="https://agentmods.dev/badge/commands/iwritec0de/app-dev/audit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/iwritec0de/app-dev/audit"><img src="https://agentmods.dev/badge/commands/iwritec0de/app-dev/audit.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00978 |
| Opus 5.5 | $0.00007 | $0.00391 |
| Sonnet 5.5 | $0.00003 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Audit
Scan a Next.js project for common issues, anti-patterns, and misconfigurations.
Load the nextjs-expert skill for App Router patterns and security best practices.
Usage
/audit [--focus routing|components|performance|all]
Arguments
Parse $ARGUMENTS to extract:
- --focus (optional, default:
all)routing— Route structure, missing error/loading boundaries, middleware issuescomponents— Client/server component misuse, missinguse client, prop drillingperformance— Bundle size, unoptimized images, unnecessary client-side JSall— Run everything
Instructions
1. Detect Next.js Version & Router
cat package.json | grep -E '"next"'
ls app/ 2>/dev/null && echo "App Router"
ls pages/ 2>/dev/null && echo "Pages Router"
ls next.config.* 2>/dev/null
2. Routing Audit
App Router:
- Search for missing
error.tsxboundaries in route segments - Search for missing
loading.tsxwhere data fetching occurs - Check for missing
not-found.tsxat the root - Verify
layout.tsxexists at the root - Check for route groups
(group)organization - Look for parallel routes and intercepting routes usage
- Verify
generateStaticParamsis used for dynamic routes that could be static - Check middleware.ts for correctness (matcher patterns, edge runtime compatibility)
Pages Router:
- Check for
_app.tsx,_document.tsx,_error.tsx - Look for
getStaticPropsvsgetServerSidePropsusage (prefer static when possible) - Check for missing
getStaticPathson dynamic routes
3. Component Audit
Search for:
- Missing
'use client'— Components using hooks (useState,useEffect,useRef) without the directive - Unnecessary
'use client'— Components marked client that don't need to be (no hooks, no browser APIs) - Server component data fetching —
fetch()calls in server components without proper caching directives - Large client components — Components with
'use client'that import heavy libraries (could split) - Prop drilling — Deep prop passing that should use server components or context
- Missing Suspense boundaries — Async server components without Suspense wrappers
- Direct DOM manipulation —
document.orwindow.without proper guards
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.
- 1mo ago First seen · 114 lines · 17 tokens per session scan A 7404dfcc9e6d
audit is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 6mo ago), licensed MIT. It adds 17 tokens to every session and 978 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
cloudflare-durable-objects:debug
Interactive Durable Objects debugging workflow. Diagnoses common DO errors, configuration issues, and runtime problems with step-by-step troubleshooting.
cloudflare-durable-objects:migrate
Interactive Durable Objects migration assistant. Guides through new class creation, renaming, deletion, and transfer migrations with validation.
cloudflare-durable-objects:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-workflows:debug
Interactive debugging for failing workflow instances. Use when user reports workflow errors, instances stuck, or deployment failures.