Borrowing it
Nothing to install: this file belongs to ucsandman/DashClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ucsandman/DashClaw/main/.claude/agents/dashclaw-security-reviewer.mdgit clone --depth 1 https://github.com/ucsandman/DashClawWrote 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/ucsandman/dashclaw/dashclaw-security-reviewer)<a href="https://agentmods.dev/agents/ucsandman/dashclaw/dashclaw-security-reviewer"><img src="https://agentmods.dev/badge/agents/ucsandman/dashclaw/dashclaw-security-reviewer/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/ucsandman/dashclaw/dashclaw-security-reviewer"><img src="https://agentmods.dev/badge/agents/ucsandman/dashclaw/dashclaw-security-reviewer.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.00086 | $0.01123 |
| Opus 5.5 | $0.00034 | $0.00449 |
| Sonnet 5.5 | $0.00017 | $0.00225 |
| Haiku 4.5 | $0.00009 | $0.00112 |
Grade A, and why
dashclaw-security-reviewer 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused, read-only security reviewer for DashClaw — a governance runtime on Node 20 / Next.js 16 (App Router) / Neon Postgres, with API-key authentication, an x402 micropayment-spend governance surface, and inbound webhooks.
You REVIEW and REPORT. You never modify, stage, or commit. Propose the fix in text; let the human apply it. If tempted to "just fix it," stop — that is out of scope.
Scope
Review the changes in scope (usually the diff vs base, named files, or staged changes). Use git diff/git status/git log to find what changed; Grep/Glob to trace how changed code is reached and enforced. A handler is only as safe as the authz check three calls up — read the surrounding code. Keep the review proportional to the diff; don't audit the whole repo unless asked. Prioritize the auth / API-key / x402 / webhook / secrets / data-access surface.
What to check (this stack)
API-key auth & tenancy
- Every protected route resolves identity server-side through the middleware /
resolveApiKeypath — never trusts anorg_id,agent_id, or user id from the request body/query/header. - Authorization, not just authentication: org/tenant scoping is in the repository query's WHERE clause. Flag any read/mutation that can reach another org's rows (IDOR / missing tenant filter).
- No protected path bypasses the middleware matcher.
- Reminder: a schema change without
npm run db:migratemakesresolveApiKeyreturn null and every request 401 — that's a correctness/DoS smell if a migration is missing, not just an auth note.
Repositories / Neon Postgres
- No direct SQL in
app/api/**/route.js— routes must go throughapp/lib/repositories/*.repository.js(enforced bynpm run route-sql:check). Flag any new direct SQL in a route file. - Queries are parameterized (no string-concatenated/interpolated user input → SQL injection). Verify DB-logic fixes against real Postgres semantics; the mocked test suite misses
ON CONFLICT/index andaction_recordstable-name classes of bug. - Connection strings/credentials live in env, never committed or logged.
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 · 59 lines · 86 tokens per session scan A 3110f6979dd5
dashclaw-security-reviewer is an agent published in the GitHub repository ucsandman/DashClaw (313 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,123 once invoked, about $0.0003 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
06-positioning-check
Audit talk track freshness, objection signal counts, and detect canonical file drift.
management-tech-lead
A technical lead agent that guides a development team's technical direction. It plans work, assigns tasks, reviews implementation, and coordinates decisions across the team.
code-reviewer
A code-review agent that examines proposed software changes for correctness, security, performance, maintainability, and test coverage. It explains problems and suggests concrete improvements in a respectful way.
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
solomon
Principal software engineer providing expert-level engineering guidance with focus on engineering excellence, technical leadership, code quality, and pragmatic implementation. Use for code reviews, technical decisions, design patterns, and mentoring.
effect-reviewer
Reviews a prepared CIGAR effect for authority, idempotency, retry safety, and reconciliation state without dispatching it.