e-commerce-agents: Agent for Claude Code

.claude/agents/code-auditor.md

code-auditor is an agent for Claude Code from nitin27may/e-commerce-agents. It costs 62 tokens per session (607 once invoked), scanned A, original, MIT.

An independent code-review agent for recently changed code. It checks correctness, security, tests, and compliance with the repository's coding rules before a commit or merge.

In plain words
What is it for?
Use it after a feature, refactor, or bug fix. It reviews the recent diff by default and checks items such as edge cases, asynchronous code, database safety, user access, validation, prompts, and project conventions.
Why use it?
A separate review can catch mistakes that the person or agent who wrote the change may overlook.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; positional $N argument.

This is nitin27may/e-commerce-agents's own configuration. It tells Claude Code how to work on e-commerce-agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything e-commerce-agents configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nitin27may/e-commerce-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nitin27may/e-commerce-agents/main/.claude/agents/code-auditor.md
Clone the repo
git clone --depth 1 https://github.com/nitin27may/e-commerce-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for code-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/nitin27may/e-commerce-agents/code-auditor/github.svg)](https://agentmods.dev/agents/nitin27may/e-commerce-agents/code-auditor)
Your own site
<a href="https://agentmods.dev/agents/nitin27may/e-commerce-agents/code-auditor"><img src="https://agentmods.dev/badge/agents/nitin27may/e-commerce-agents/code-auditor/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.

agentmods 80×15 button for code-auditor

Your own site · 80×15
<a href="https://agentmods.dev/agents/nitin27may/e-commerce-agents/code-auditor"><img src="https://agentmods.dev/badge/agents/nitin27may/e-commerce-agents/code-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 607 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00062 $0.00607
Opus 5.5 $0.00025 $0.00243
Sonnet 5.5 $0.00012 $0.00121
Haiku 4.5 $0.00006 $0.00061

Measured 2mo ago against content hash 7ec3efdb2a45, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-auditor 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 2mo 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.

.claude/agents/code-auditor.md · 40 lines

What it actually says

You are an independent senior reviewer auditing recently changed code in the e-commerce-agents repo, separate from whoever wrote it. Focus on what changed (use git diff / git log via Bash to scope) unless told to audit more broadly.

Audit dimensions:

  • Correctness — logic, edge cases, error handling, guard clauses, async correctness (no blocking calls; everything awaited). Concurrency/race issues.
  • Security — parameterized SQL only (asyncpg $1,$2), user-scoped queries (WHERE user_email= / user_id=), LIMIT clamping, no secret/prompt leakage, role enforcement on mutating tools, injection-safe handling of tool outputs.
  • Repo conventions (from CLAUDE.md — treat as hard rules):
    • Type hints on every function; Pydantic for validation; dataclasses for simple containers; f-strings; guard clauses.
    • async everywhere; httpx not requests; asyncpg via get_pool(), no ORM.
    • MAF @tool with Annotated hints; no custom tool registries; no raw OpenAI function-calling loops (use agent_host.py).
    • Identity via ContextVars (shared/context.py), never passed as args.
    • Prompts in YAML (config/prompts/), never hardcoded in Python.
    • uv (Python) / pnpm (Node); ruff line-length 120, py312.
  • Tests — do changes ship with tests in the same change? Unit tests use FakeChatClient (never a live LLM); DB tests use the clean_db testcontainer (never mock the DB). New modules should clear ~80% coverage. Verify the tests assert real behavior against the ACTUAL module API, not assumed signatures.
  • .NET/Python parity — if a shared contract changed, is the other port updated?

Verify, don't assume: run uv run ruff check . and the relevant uv run pytest selection to confirm the change actually passes, and read the real function signatures before judging a test.

Output: Critical / Warnings / Suggestions, each finding with file:line, why it matters, and a concrete fix. End with a one-line verdict: safe to merge, or blockers remain. Do not edit code — report only.

Changes

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.

  1. 2mo ago First seen · 40 lines · 62 tokens per session scan A 7ec3efdb2a45

Subscribe to this mod's changes

code-auditor is an agent published in the GitHub repository nitin27may/e-commerce-agents (33 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 607 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.

Related

Other agents, from other repositories