Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add musingfox/cc-plugins/plugin install deepenWrote 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/musingfox/cc-plugins/survey)<a href="https://agentmods.dev/skills/musingfox/cc-plugins/survey"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/survey/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/musingfox/cc-plugins/survey"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/survey.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.00035 | $0.00754 |
| Opus 5.5 | $0.00014 | $0.00302 |
| Sonnet 5.5 | $0.00007 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
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 10d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey
1. Scope
If $ARGUMENTS is non-empty, that string is the scope. Skip hotspot inference. Tell the user the chosen scope in one line, then go to Context.
Otherwise run, from the repository root:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/hotspots.sh"
Read the scope: line.
scope: hotspot— the first three ranked paths are the scope (hotspots.sh prints up to five).scope: wide— the whole tree is the scope; keep the ranked list as hints. If history is thin (windowbelow 10 or an empty log), say in the one-line scope message that the whole tree is being surveyed because history is thin.
If hotspots.sh exits 1 (not a git repository) and $ARGUMENTS is empty, stop. Ask in plain prose for a direction. That is an input question, not permission.
Tell the user the chosen scope in one line before anything else runs: the direction, the hotspot paths, or "whole tree".
2. Context
Before dispatch, read CONTEXT.md if it exists and any ADRs under docs/decisions/ or docs/adr/, the directories /adr:adr looks in first. They constrain what a candidate may contradict.
3. Explore
Print the one-line scope and how many explorers will run. Dispatch them in one message, at most three.
For each scope path (or one explorer for the whole tree), call:
Agent(subagent_type: "deepen:explorer", prompt: "Report path: /tmp/viz/<project>/deepen-explorer-<timestamp>-<n>.md\nScope: <path or whole tree>\n")
<project> is $(basename "$PWD"). Timestamp the files so a stale report from an earlier run cannot be mistaken for this one. Explorers run in parallel. Print nothing else until they return.
If a report file is missing after dispatch, say which scope produced nothing and continue with the others.
4. Read
Do not Read an explorer report whole. For each report path you dispatched in step 3 that exists, take only:
sed -n '/^## Summary/,/^## Notes/p' /tmp/viz/<project>/deepen-explorer-<timestamp>-<n>.md
That range stops at ## Notes (inclusive of the heading, exclusive of the trail). Never load ## Notes.
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.
- 10d ago Changed · -1 lines · +2 tokens per session 08e4e701bdfa
- 14d ago Changed 1e2057398e90
- 1mo ago First seen · 78 lines · 33 tokens per session scan A 0a07488589ce
survey is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 754 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-09-11.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…