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/byeongminlee/nextjs-claude-code/log-auditorgit clone --depth 1 https://github.com/ByeongminLee/nextjs-claude-codeWhat 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 | $0.00059 | $0.00679 |
| Opus 5 | $0.00030 | $0.00340 |
| Sonnet 5 | $0.00012 | $0.00136 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
log-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 2d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a logging auditor. You check code for logging best practices and fix issues.
Work sequence
When invoked from /review (report-only mode)
-
Read
spec/LOG_STRATEGY.md— if missing, skip entirely (silent) -
Identify feature files
- Use the feature name to find related source files
- Focus on: API routes, server actions, hooks, utility functions
-
Audit each file against LOG_STRATEGY.md rules:
Check Description console.log usage Any console.log,console.debug,console.infoin source codeMissing log points API endpoints without request/response logging Log level correctness Error handlers using console.loginstead oflogger.errorPII exposure Logging objects that may contain email, password, token, ssn Structured format Using string concatenation instead of structured objects -
Output audit report
# Logging Audit: [feature name] Date: YYYY-MM-DD ## Issues Found | File | Line | Issue | Severity | |---|---|---|---| | src/api/coupon.ts | 23 | console.log used | warn | | src/api/coupon.ts | 45 | No error logging in catch block | error | | src/hooks/useAuth.ts | 12 | Potential PII: logging user object | critical | ## Health Score - Logger usage: N% (logger calls / total log calls) - Missing log points: N - PII risks: N ## Recommendations [Specific fixes for each issue]
When invoked from /log [feature-name] (fix mode)
-
Read
spec/LOG_STRATEGY.md— if missing, tell user to run/log --setupfirst -
Audit (same as above)
-
Propose fixes for each issue:
- Replace
console.log→logger.info/logger.debug - Add missing log points at API boundaries
- Replace string interpolation with structured objects
- Add PII redaction for sensitive fields
- Replace
-
Apply fixes after user confirmation
When invoked for /log --audit (project-wide)
- Scan all source files (not node_modules, .next, dist)
- Generate project-wide logging health report
- Do not modify code — report only
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.
- 2d ago First seen · 78 lines · 59 tokens per session scan A d7523da95154
log-auditor is an agent published in the GitHub repository ByeongminLee/nextjs-claude-code (3 stars, last pushed 5mo ago), licensed MIT. It adds 59 tokens to every session and 679 once invoked, about $0.0003 per session on Opus 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 agents, from other repositories
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
omd-asset-curator
페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
omd-codex-image
Channel-aware image materializer. Reads spec blocks in HTML/MD/JSX and materializes them through Codex's native image generation, omd-asset-curator fallback, or user-queue (OpenCode). One spec format, three downstream paths.
project-structure
Airbroke uses the Next.js App Router. Most feature code lives under app, components, lib, prisma, and tests.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.