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/eddiebelaval/squireWrote 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/eddiebelaval/squire/integration-audit)<a href="https://agentmods.dev/commands/eddiebelaval/squire/integration-audit"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/integration-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.00000 | $0.01764 |
| Opus 5 | $0.00000 | $0.00882 |
| Sonnet 5 | $0.00000 | $0.00353 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
integration-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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integration-audit - Full-Stack Integration Audit with Visual Report
Perform a comprehensive audit of all features, checking whether each feature is fully integrated across every layer of the stack (frontend UI, API routes, database/Supabase, state management, types). Output the results as an interactive HTML visualization using the Factory-inspired design system.
Arguments
/integration-audit [project-path] where project-path is optional:
- No argument: audit the current working directory
- A directory path: audit that project specifically
- Example:
/integration-audit ~/Development/Homer
How This Differs From /audit
/auditchecks codebase health (security, dead code, type safety)/integration-auditchecks feature completeness — is every feature wired end-to-end?- Output is always an interactive HTML artifact (not a text report)
Phase 1: Discovery (Parallel Scans)
Launch parallel Explore agents (subagent_type: Explore) to scan each layer simultaneously. Each agent returns structured findings.
Agent 1: API Routes Scan
Scan for all API route handlers. For Next.js App Router projects:
- Glob:
**/app/api/**/route.ts,**/app/api/**/route.tsx - For each route, extract: path, HTTP methods (GET/POST/PUT/PATCH/DELETE), auth checks (presence of getUser/session/auth middleware), database calls (supabase/prisma/drizzle references), request/response types
- Also check for: server actions in
**/actions/**or"use server"directives
Agent 2: Frontend Pages & Components Scan
Scan for all pages and feature components:
- Pages:
**/app/**/page.tsx,**/pages/**/*.tsx - Components:
**/components/**/*.tsx,**/features/**/*.tsx - For each, extract: API calls (fetch, axios, useSWR, useQuery, server actions), form submissions, state store usage, route links/navigation
- Identify UI shells: components with placeholder text, TODO comments, or hardcoded mock data
Agent 3: Database & Schema Scan
Scan for database schema and access patterns:
- Supabase: migration files, type generation files, RLS policies
- Schema files:
**/schema.ts,**/schema.sql,**/migrations/** - Type files: shared types/interfaces that define data models
- For each table/entity, extract: table name, columns, relationships, RLS policies, which API routes access it
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 · 159 lines · 0 tokens per session scan A 7323ce541129
integration-audit is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,764 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-03.
Other commands, from other repositories
detectar-ambiguedad
Detectar ambigüedades y contradicciones en specs de forma exhaustiva.
fix
Fix validation errors and test failures (Phase 3 support).
scan
Analyze an existing codebase. Maps structure, architecture, conventions, and concerns.
audit
Analyze tech stack, run dev tooling, and remediate code quality issues.
go-build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
checklist
Generate a custom checklist for the current feature based on user requirements.