survey-code

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.

In plain words
What is it for?
Use it to inspect a repository for files, architecture patterns, implementation constraints, and evidence related to a planned task.
Why use it?
It gives developers a documented understanding of existing patterns, constraints, and risks before they change the code.

Agent

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.

agentmods
npx agentmods add agents/nirecom/agents/survey-code
Clone the repo
git clone --depth 1 https://github.com/nirecom/agents
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 480 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00029 $0.00480
Opus 5 $0.00015 $0.00240
Sonnet 5 $0.00006 $0.00096
Haiku 4.5 $0.00003 $0.00048

Measured yesterday against content hash 74f6fb3513c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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 · 48 lines

What it actually says

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:

  1. Candidate files and areas matching the task claims
  2. Existing patterns, architectural constraints, and relevant line numbers
  3. 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.
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. yesterday 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 2d ago), licensed MIT. It adds 29 tokens to every session and 480 once invoked, about $0.0001 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens