What is critique-survey?

A survey-review command that examines an existing questionnaire for leading wording, tempting but careless answer choices, and missing structure.

Use it to review survey text, a survey URL, or a survey file and receive a ranked issue list, rewrites, and an overall assessment.

It identifies questions that may bias answers or produce low-quality information, then suggests concrete rewrites.

critique-survey — Command for Claude Code by ooiyeefei/ccc

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.

Clone the repo

git clone --depth 1 https://github.com/ooiyeefei/ccc

Made for: Claude Code.

Or install rethink-surveys, the plugin that ships this one along with the rest of its 1 skill, 3 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ooiyeefei/ccc/critique-survey/github.svg)](https://agentmods.dev/commands/ooiyeefei/ccc/critique-survey)

Your own site

<a href="https://agentmods.dev/commands/ooiyeefei/ccc/critique-survey"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/critique-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/ooiyeefei/ccc/critique-survey"><img src="https://agentmods.dev/badge/commands/ooiyeefei/ccc/critique-survey.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,368 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00026	$0.01368
Opus 5.5	$0.00010	$0.00547
Sonnet 5.5	$0.00005	$0.00274
Haiku 4.5	$0.00003	$0.00137

Measured 2mo ago against content hash 30b705e12971, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

critique-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 2mo 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.

plugins/rethink-surveys/commands/critique-survey.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Critique Survey

Take an existing survey (pasted text, URL, or file) and return a Jarrett-style review with:

A punch-list of issues (severity-ranked)
Concrete rewrites for the worst 3–5
A verdict on the overall instrument

Usage

/critique-survey

The user will paste, link, or attach. If they paste a URL, fetch it (WebFetch). If a file path, read it. If they paste text directly, work from that.

Process

Always invoke the rethink-surveys skill first.

Step 1 — Catalog the questions

Read every question. Number them. For each, capture:

The question text (verbatim)
Answer format (open / single / multi / scale / etc.)
Position in flow (early / mid / late)
Any branching shown
Any consent or contact treatment

If the survey is long (>15 Qs), summarize structurally before diving in.

Step 2 — Apply the seven principles

For each question, check against:

Past behavior, not hypotheticals. Flag any "Would you..." / "Will you..." / "Do you think..."
No pre-signaling the right answer. Flag "Most people..." / loaded adjectives in option labels / leading question stems.
Open-ended before narrowing. Is there at least one open question early? Is it forced into a checkbox structure?
Screening / diagnosis / segmentation separation. Are demographic questions polluting the diagnostic flow?
No double-barreled questions. Flag any "X and Y?" question.
Behavioral anchors over Likert. Flag any 1-5/1-7 with vague anchors ("strongly agree"). Suggest behavioral replacements where possible.
Honest length claim. If a length is stated, estimate the actual time and flag mismatch.

Step 3 — Apply the 4-part structural check

Tag each Q with which part it serves: discovery / diagnostic / intent / segmentation. Then check:

Discovery missing? Survey is checkbox-only — won't capture novelty. Recommend adding one open Q at start.
Diagnostic missing or shallow? Won't be analyzable across users — recommend adding severity/frequency.
Intent missing? Won't surface demand signal. Recommend adding WTP buckets or top-3 priority.
Segmentation missing? Won't enable cohorting. Recommend at minimum a single respondent-type Q.
Same part hit by 3+ questions? Survey is bloated in one direction. Recommend cuts.

Read the full file on GitHub · 169 lines

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.

2mo ago First seen · 169 lines · 26 tokens per session scan A 30b705e12971

Subscribe to this mod's changes

critique-survey is a command published in the GitHub repository ooiyeefei/ccc (499 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 1,368 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-30.

Research

critique-survey next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
critique-surveyooiyeefei/ccc	Command	499	8d ago	MIT	A	26	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code