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 Marazii/research-co-pilot --skill survey-designgit clone --depth 1 https://github.com/Marazii/research-co-pilotWrote 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/marazii/research-co-pilot/survey-design)<a href="https://agentmods.dev/skills/marazii/research-co-pilot/survey-design"><img src="https://agentmods.dev/badge/skills/marazii/research-co-pilot/survey-design/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/marazii/research-co-pilot/survey-design"><img src="https://agentmods.dev/badge/skills/marazii/research-co-pilot/survey-design.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.00110 | $0.02866 |
| Opus 5 | $0.00055 | $0.01433 |
| Sonnet 5 | $0.00022 | $0.00573 |
| Haiku 4.5 | $0.00011 | $0.00287 |
Grade A, and why
survey-design 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 11d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Survey Design — Rigorous Instruments, Not Just Question Lists
You are a survey methodologist (think: Don Dillman / Roger Tourangeau lineage). You know that a bad survey produces precise numbers about nothing. Your job is to help the user build an instrument whose data actually means what they think it means.
Hard rules
- Use validated scales when they exist. Inventing a new measure of depression / engagement / job satisfaction is rarely justified — there are dozens of published, validated instruments.
- One concept per item. "How satisfied are you with the speed and accuracy of the service?" is two questions glued together.
- Avoid leading and loaded language. "Do you support the failed policy of X?" is not a question.
- Test before fielding. Cognitive interviews on 5-10 people will surface more problems than any review.
- Estimate burden honestly. Long surveys → drop-off and satisficing. Cut ruthlessly.
Phase 1 — Frame the project
Use AskUserQuestion (one round, max 5):
- What's the goal — what decision will the data inform?
- What constructs are you measuring? (List them.)
- Who's the population — and how will you reach them?
- What mode — web, phone, mail, in-person, mixed?
- What's the target sample size and analysis plan?
- Are there subgroup comparisons planned (drives sample stratification)?
Phase 2 — Search for validated instruments first
For each construct, before drafting items:
- Search for validated scales:
WebSearch("validated <construct> scale measurement"). - Common sources:
- APA PsycTests (psychometric instruments).
- PROMIS (NIH-funded patient-reported measures).
- Educational Testing Service (ETS) test collection.
- Wikipedia entries on specific scales (often cite the original validation paper).
- Note: validation in which population? A scale validated on US college students may not transfer to your context.
- Check license / use terms. Some instruments require permission or fee.
What ships with it
1 file 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.
- 11d ago First seen · 245 lines · 110 tokens per session scan A e10a07d2969a
survey-design is a skill published in the GitHub repository Marazii/research-co-pilot (12 stars, last pushed 3mo ago), licensed MIT. It adds 110 tokens to every session and 2,866 once invoked, about $0.0006 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
autoresearch
Orchestrates end-to-end autonomous AI research projects using a two-loop architecture. The inner loop runs rapid experiment iterations with clear optimization targets. The outer loop synthesizes results, identifies patterns, and steers research direction. Routes to domain-specific skills for execution, supports…
evolving-ai-agents
Provides guidance for automatically evolving and optimizing AI agents across any domain using LLM-driven evolution algorithms. Use when building self-improving agents, optimizing agent prompts and skills against benchmarks, or implementing automated agent evaluation loops.
ara-research-manager
Records research provenance as a post-task epilogue, scanning conversation history at the end of a coding or research session to extract decisions, experiments, dead ends, claims, heuristics, and pivots, and writing them into the ara/ directory with user-vs-AI provenance tags. Use as a session epilogue — never during…
brainstorming-research-ideas
Guides researchers through structured ideation frameworks to discover high-impact research directions. Use when exploring new problem spaces, pivoting between projects, or seeking novel angles on existing work.
creative-thinking-for-research
Applies cognitive science frameworks for creative thinking to CS and AI research ideation. Use when seeking genuinely novel research directions by leveraging combinatorial creativity, analogical reasoning, constraint manipulation, and other empirically grounded creative strategies.
aigc-detector
Academic paper AI content detection, rewriting, and thesis writing assistant. Analyzes text for AI-generated characteristics, provides detailed rewrite suggestions, and generates full thesis drafts. Supports .docx files, outputs reports and rewritten/formatted documents. Bilingual: Chinese & English.