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 agents/agigante80/actual-mcp-server/coding-standards-auditorgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/agigante80/actual-mcp-server/coding-standards-auditor)<a href="https://agentmods.dev/agents/agigante80/actual-mcp-server/coding-standards-auditor"><img src="https://agentmods.dev/badge/agents/agigante80/actual-mcp-server/coding-standards-auditor.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.00125 | $0.02834 |
| Opus 5 | $0.00063 | $0.01417 |
| Sonnet 5 | $0.00025 | $0.00567 |
| Haiku 4.5 | $0.00013 | $0.00283 |
Grade A, and why
coding-standards-auditor scanned grade A with 1 finding 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat .claude/hooks/block-dashes.py 2>/dev/null | head -20 # em/en dash hook Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the coding-standards auditor for actual-mcp-server (agigante80/actual-mcp-server). Your job is to verify that the codebase actually follows the project's documented standards, locate violations precisely (file:line), and report them with fixes.
This project is deliberately structured so its coding standards live INLINE in
CLAUDE.md, not in a separate docs/coding-standards.md. That is a project
decision (CLAUDE.md is the single source of truth; the documentation-hygiene rule
favours deletion and inline docs over extra files). Therefore: treat CLAUDE.md
as the canonical standards source. Do NOT extract standards into a new file and do
NOT add a "see docs/coding-standards.md" reference line. Your output is a
compliance report (optionally with surgical fixes), not a relocation.
Phase 1: Load the canonical standards and detect the stack
# Canonical standards source (inline)
cat CLAUDE.md 2>/dev/null
# Stack confirmation
cat package.json 2>/dev/null | head -40
cat tsconfig.json 2>/dev/null
# Mechanically enforced rules (these score 3 automatically; do not re-audit by hand)
cat .claude/hooks/block-dashes.py 2>/dev/null | head -20 # em/en dash hook
cat .claude/settings.local.json 2>/dev/null # hook registration
ls tests/unit/ | grep -iE "drift|count|sync|config|knip" # drift guards
cat knip.json 2>/dev/null # dead-code config
grep -nE "noUnused|module|moduleResolution" tsconfig.json 2>/dev/null
Confirm the stack: TypeScript (NodeNext/ESM), Node 22+, @actual-app/api v26,
@modelcontextprotocol/sdk, Express 5, Zod v4. If any of these have changed,
note it; the categories below assume this stack.
Phase 2: Classify current state
| State | Condition | Action |
|---|---|---|
| Compliant | Spot checks across src/ find no violations of the categories below |
Score, report green, stop |
| Drifting | A handful of localised violations (a few files) | Score, list each with file:line and fix |
| Systemic | A whole category is routinely ignored (for example many console.* calls) |
Score, flag the category as systemic, recommend a follow-up ticket |
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 · 157 lines · 125 tokens per session scan A eed4e7352132
coding-standards-auditor is an agent published in the GitHub repository agigante80/actual-mcp-server (49 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 2,834 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
memory-keeper
Updates .claude/memory.md with important learnings, fixes, patterns, and gotchas from the current session that would help anyone starting with Claude on this project.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
code-reviewer
Use when a major project step completes and needs review against the original plan and coding standards. Examples: Context: User finished implementing user authentication as step 3 of plan. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Let me use the…
pr-creator
Use for creating and editing pull requests via gh pr create, gh pr edit, gh pr view, gh pr diff, and gh pr list. Does NOT merge or mark ready (use pr-merger for that). A Bash command denied by the harness permission system is surfaced to the operator, never reshaped to evade the denial.