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 skills/cookys/autopilot/surveynpx skills add cookys/autopilot --skill surveygit clone --depth 1 https://github.com/cookys/autopilotWrote 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/skills/cookys/autopilot/survey)<a href="https://agentmods.dev/skills/cookys/autopilot/survey"><img src="https://agentmods.dev/badge/skills/cookys/autopilot/survey.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.00106 | $0.01190 |
| Opus 5 | $0.00053 | $0.00595 |
| Sonnet 5 | $0.00021 | $0.00238 |
| Haiku 4.5 | $0.00011 | $0.00119 |
Grade A, and why
survey 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey -- Technology Research
Routing overlap? If this intent better matches a sibling skill, redirect per references/routing-tiebreaks.md (prefer external evidence research over internal priority debate).
Two independent agents (researcher + skeptic) search in parallel, bringing different perspectives to avoid anchoring bias and recency bias.
Trigger
| Method | When |
|---|---|
| Manual | User says "survey", "research", "investigate", "what does the industry do" |
| Signal suggestion | Plan Mode / brainstorming detects tech selection / architecture decision / uncertainty -> suggest (user confirms before running) |
Suggestion template (when signal detected):
"This decision involves tech selection. Suggest running
/surveyto research industry practices first. Proceed?"
Boundary
- Produce recommendation, marked as suggestion -- attach reasoning and preconditions so user can judge applicability
- No code -- research only
- No auto-trigger -- signal only suggests, user confirms
Flow
Step 1: Scope the Research
Extract from user input:
- Topic: what to research (e.g. "WS compression options")
- Constraints: known limits (e.g. "must support C++20", "latency < 1ms")
- Existing bias: does user already lean toward something? (researcher should specifically probe that option's weaknesses)
If input is vague (e.g. "look into cache"), ask one clarifying round before dispatch.
Step 2: Parallel Dispatch
Model routing: Read .claude/model-routing-config.md if exists; otherwise defaults from references/model-routing.md. Survey agents map to researcher → default: model: "sonnet" (needs web search tools, so NOT plan mode).
Spawn researcher + skeptic simultaneously. Skeptic does NOT wait for researcher -- independent search finds different angles.
Agent tool:
name: "survey-researcher"
subagent_type: "general-purpose"
model: "sonnet" # from model-routing config (researcher role)
run_in_background: true
prompt: -> references/prompts.md #Researcher
Agent tool:
name: "survey-skeptic"
subagent_type: "general-purpose"
model: "sonnet" # from model-routing config (researcher role)
run_in_background: true
prompt: -> references/prompts.md #Skeptic
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 137 lines · 106 tokens per session scan A 6bd14803c265
survey is a skill published in the GitHub repository cookys/autopilot (11 stars, last pushed yesterday), licensed MIT. It adds 106 tokens to every session and 1,190 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…