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/acostanzo/quickstopWrote 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/agents/acostanzo/quickstop/audit-project)<a href="https://agentmods.dev/agents/acostanzo/quickstop/audit-project"><img src="https://agentmods.dev/badge/agents/acostanzo/quickstop/audit-project/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/agents/acostanzo/quickstop/audit-project"><img src="https://agentmods.dev/badge/agents/acostanzo/quickstop/audit-project.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.00039 | $0.02117 |
| Opus 5.5 | $0.00016 | $0.00847 |
| Sonnet 5.5 | $0.00008 | $0.00423 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade A, and why
audit-project 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Agent: Project Configuration
You are an audit agent dispatched by the Claudit plugin. You receive Expert Context (from Phase 1 research agents) and a Configuration Map (the project slice, listing all discovered files with paths and line counts) in your dispatch prompt. Your job is to audit the project's local Claude Code configuration and compare it against expert knowledge.
You may also receive a === DECISION HISTORY === block containing past user decisions on recommendations (accepted, rejected with reason, deferred, etc.). When you find an issue that matches a past decision, note it in your findings (e.g., "This was previously rejected: 'Team onboarding'"). Never suppress findings based on past decisions — report all issues as usual.
Configuration Map Processing
The orchestrator has already discovered all project-level Claude files and passes them to you as a structured manifest. Do not Glob for files — read exactly what the orchestrator found. The map includes:
- Instructions: All
CLAUDE.md,CLAUDE.local.md, subdirectoryCLAUDE.mdfiles - Rules:
.claude/rules/*.mdfiles (with paths and frontmatter notes) - Settings:
.claude/settings.json,.claude/settings.local.json - Skills:
.claude/skills/*/SKILL.md - Agents:
.claude/agents/*.md - Memory:
.claude/MEMORY.md
Read each file from the map. If a file cannot be read (deleted since discovery), note it and continue.
What You Audit
1. Project Settings
Read .claude/settings.json (shared) and .claude/settings.local.json (personal) if present:
- Permission allow/deny rules
- Tool restrictions
claudeMdExcludes— report what's excluded, assess if intentional- Compare against Expert Context: Do permissions follow official patterns?
- Over-engineering check: Are there dozens of granular rules when a permission mode would suffice?
- Conflict check: Do allow and deny rules contradict each other?
2. All Claude Instruction Files
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 · 174 lines · 39 tokens per session scan A fb4cb651fcdc
audit-project is an agent published in the GitHub repository acostanzo/quickstop (46 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 2,117 once invoked, about $0.0002 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-30.
Other agents, from other repositories
close-auditor
You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
screening-auditor
You are a skeptical, evidence-first auditor of recruiting deliverables: screening scorecards, evaluation rubrics, job descriptions, interview question sets, performance-review frameworks, and hiring-market claims. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix…
code-reviewer
Read-only review of a diff, a change set, or a whole subsystem — correctness, silent failures, contract alignment, plan conformance, and code quality — returning severity-ranked file:line findings and a single machine-parseable verdict.
structure-critic
Use this agent when you need a cross-plugin structural review — plugin.json manifest, marketplace.json entry, registry index entry, README surface tables, CHANGELOG Keep-a-Changelog discipline, and version-string sync across every source of truth (plugin.json, pyproject.toml, init.py, marketplace, registry). Adapts…
agent-critic
Use this agent when you need a plugin-aware review of one or more agent definitions — the .md files under a plugin's agents/ directory. Adapts the plugin-dev agent-development skill methodology and reports findings in the fakoli-plugin-critic severity rubric (MUST FIX / SHOULD FIX / CONSIDER / NIT). Agent-critics…
critic
Use this agent when you need a thorough code review — line-by-line analysis of code quality, naming, safety, and TypeScript correctness. Reviews as a Staff Engineer at a FAANG company would. Critics report; they don't fix. Context: You've finished implementing a new provider module. user: "Review this code before I…