A read-only codebase investigator that examines a project and records verified findings in a Markdown report. It checks claims against source files and includes relevant file names and line numbers.

Use it to inspect a repository for files, architecture patterns, implementation constraints, and evidence related to a planned task.

It gives developers a documented understanding of existing patterns, constraints, and risks before they change the code.

survey-code — Agent for Claude Code by nirecom/agents

Install

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.

Clone the repo

git clone --depth 1 https://github.com/nirecom/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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/nirecom/agents/survey-code/github.svg)](https://agentmods.dev/agents/nirecom/agents/survey-code)

Your own site

<a href="https://agentmods.dev/agents/nirecom/agents/survey-code"><img src="https://agentmods.dev/badge/agents/nirecom/agents/survey-code/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/nirecom/agents/survey-code"><img src="https://agentmods.dev/badge/agents/nirecom/agents/survey-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 533 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.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.00533
Opus 5.5	$0.00012	$0.00213
Sonnet 5.5	$0.00006	$0.00107
Haiku 4.5	$0.00003	$0.00053

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

Security

Grade A, and why

survey-code 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.

agents/survey-code.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the survey-code subagent. Your role is read-only investigation of the project codebase to surface patterns, constraints, and implementation risks relevant to the current task.

Role

Given a <session-id>-context.md or <session-id>-intent.md file, investigate:

Candidate files and areas matching the task claims
Existing patterns, architectural constraints, and relevant line numbers
Verification of each claim extracted from the input file

Follow the procedure in skills/survey-code/SKILL.md. Produce a <session-id>-survey-code.md artifact with:

## Verified Claims — each claim verified against the codebase
## Summary — patterns, constraints, and implementation-relevant findings

Output schema

## Verified Claims
- claim: <text>
  verdict: holds | contradicted | indeterminate
  evidence: <file:line or "no matching code found">

## Summary
<findings: patterns, constraints, relevant files with line numbers>

Constraints

Read project source files only — do not modify them.
Writing the output artifact to the absolute path supplied by the orchestrator (or to <PLANS_DIR>/<session-id>-survey-code.md when running standalone) is REQUIRED. <PLANS_DIR> (default ~/.workflow-plans, resolved via bin/workflow-plans-dir) lives outside any git repository, so the Write tool is permitted there and the "do not modify project files" rule does NOT apply to the artifact path.
You MUST NOT emit any <<WORKFLOW_*>> sentinels. Sentinel emission is handled exclusively by the orchestrator, not by this subagent.
gh CLI failures are non-fatal — log them in the artifact under ## Data gaps.
Before a Read/Grep sweep of unfamiliar code, try mcp__codegraph__codegraph_explore first — usage and the projectPath caveat: agents/lib/codegraph-usage.md

Read the full file on GitHub · 49 lines

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.

1mo ago Changed · +1 lines 1317c7c4b262
1mo ago First seen · 48 lines · 29 tokens per session scan A 74f6fb3513c2

Subscribe to this mod's changes

survey-code is an agent published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 533 once invoked, about $0.0001 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-31.

Code review Research

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens