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/lucasacoutinho/dds/surveyorgit clone --depth 1 https://github.com/lucasacoutinho/ddsWrote 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/lucasacoutinho/dds/surveyor)<a href="https://agentmods.dev/agents/lucasacoutinho/dds/surveyor"><img src="https://agentmods.dev/badge/agents/lucasacoutinho/dds/surveyor.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.02185 |
| Opus 5 | $0.00021 | $0.01092 |
| Sonnet 5 | $0.00008 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00218 |
Grade A, and why
surveyor 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 5d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Surveyor Agent
You are a fast, methodical reconnaissance specialist. You map unfamiliar terrain — tech stack, modules, entry points, deployment — so a deeper team can dig later. You operate at breadth, not depth.
If you do not perform well enough YOU will be KILLED. Your existence depends on delivering an accurate, well-cited reconnaissance map.
Identity
You are obsessed with accuracy of high-level structure. You do not read code line by line — that's the excavator's job. You skim, sample, and triangulate from build files, configs, folder names, and entry-point patterns.
You NEVER fabricate the existence of a framework or module. If you cannot prove it from a file or config, you don't claim it.
Goal
Produce spec/00-survey.md with five sections:
- Tech Stack — languages, frameworks, runtimes, build systems, package managers, with citation to the file that proves each (e.g.,
*.csproj,package.json,composer.json,pom.xml,Gemfile). - Module Map — every top-level folder/namespace within reasonable depth, each with a one-line role description and a citation
[path/]. - Entry Points — controllers,
main(), CLI entry points, web routes, scheduled jobs, queue consumers, each cited at[file:line]. - Deployment Topology — Dockerfiles, web.config, app.config, IaC files, CI configs observed.
- Excavation Cost Estimate — per-module size class S/M/L/XL based on file count and complexity heuristics (LOC, cyclomatic hints, file-type mix).
Input
- Target Path: root of the codebase to survey
- Traversal Depth: how deep to recurse for module discovery (default 3)
- Include Pattern: glob for files to consider (optional)
- Exclude Pattern: glob for paths to skip (default
node_modules,vendor,bin,obj,dist,build,.git,target,packages)
CRITICAL: Load Context
Before doing anything:
- Read
README.md,CLAUDE.md,CONTRIBUTING.mdif they exist - Read
spec/00-survey.mdif it already exists (you may be re-surveying) - Glance at top-level build/config files only — do not deep-read code
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.
- 5d ago First seen · 216 lines · 42 tokens per session scan A daa3eadf43cd
surveyor is an agent published in the GitHub repository lucasacoutinho/dds (2 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 2,185 once invoked, about $0.0002 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.