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 skills add nirecom/agents --skill survey-codegit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/survey-code)<a href="https://agentmods.dev/skills/nirecom/agents/survey-code"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/nirecom/agents/survey-code"><img src="https://agentmods.dev/badge/skills/nirecom/agents/survey-code.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.00020 | $0.01174 |
| Opus 5.5 | $0.00008 | $0.00470 |
| Sonnet 5.5 | $0.00004 | $0.00235 |
| Haiku 4.5 | $0.00002 | $0.00117 |
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 today.
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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Investigate the codebase related to the given task.
Procedure
SVC-0 — Resolve <PLANS_DIR>
Before any tool call below that references <PLANS_DIR>, run bash "$AGENTS_MAIN_ROOT/bin/workflow-plans-dir" exactly once as one bare command — never assigned to a variable and echoed back.
Read the printed absolute path from its stdout and substitute it for every <PLANS_DIR> placeholder in the remainder of this SKILL.md. Subagent prompts must receive the resolved absolute path as a literal string (subagents cannot expand $VAR). Reuse across all subsequent in-skill steps in this invocation — do not re-resolve.
When invoked as a parallel Agent subagent by workflow-init, the orchestrator
passes artifact_path and context_path as resolved absolute strings — use
those instead of running SVC-0.
Canonical documentation: skills/_shared/resolve-plans-dir.md.
SVC-1. Claim extraction (run before reading any code):
Input precedence (read whichever exists first):
(a) the path printed by node "$AGENTS_MAIN_ROOT/bin/plan-artifact-path" --stage intent (it follows a resumed session's upstream) — preferred (post-clarify-intent calls)
(b) <PLANS_DIR>/<session-id>-context.md — fallback (pre-clarify-intent calls
from workflow-init; use "User initial prompt" and "Issue body" sections)
If neither exists: proceed to SVC-2 with an empty claim list.
Extract up to 5 behavioral/factual claims from Background/Motivation and Scope.
Target: "X is blocked", "X does Y", "X is broken", "X cannot Z". Exclude aesthetic
claims and pure preferences. Works with Japanese and English content.
SVC-2. Identify candidate files and areas using Glob and Grep. SVC-3. Read relevant source files, configs, tests, and docs. SVC-4. For each claim extracted in SVC-1, verify it against the current codebase:
verdict: holds— evidence in code confirms the claimverdict: contradicted— evidence in code contradicts the claimverdict: indeterminate— insufficient evidence to confirm or deny SVC-5. Summarize: existing patterns, architectural constraints, relevant files (with line numbers), and anything that affects implementation. SVC-6. Write findings to<PLANS_DIR>/<session-id>-survey-code.md. The file must include a## Verified Claimssection:
## Verified Claims
- claim: <text from intent.md>
verdict: holds | contradicted | indeterminate
evidence: <file:line or "no matching code found">
If no claims were extracted in SVC-1, write the section with the note "No verifiable behavioral/factual claims found in intent.md or context.md."
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.
- today Changed 0ed25e549f84
- 9d ago Changed · +1 lines 03e36ff13c5e
- 11d ago Changed ca0f9fe07149
- 21d ago Changed 28a941399509
- 1mo ago Changed · -6 lines a8bbe28c3ebb
- 1mo ago First seen · 95 lines · 20 tokens per session scan A bc8ee0581f9d
survey-code is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,174 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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…