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 unbias38/my-claude-skills --skill survey-designgit clone --depth 1 https://github.com/unbias38/my-claude-skillsWrote 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/unbias38/my-claude-skills/survey-design)<a href="https://agentmods.dev/skills/unbias38/my-claude-skills/survey-design"><img src="https://agentmods.dev/badge/skills/unbias38/my-claude-skills/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/unbias38/my-claude-skills/survey-design"><img src="https://agentmods.dev/badge/skills/unbias38/my-claude-skills/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.00072 | $0.02884 |
| Opus 5 | $0.00036 | $0.01442 |
| Sonnet 5 | $0.00014 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
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 12d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Academic Survey/Questionnaire Design
Design questionnaires that meet academic publication standards, with built-in self-evaluation based on COSMIN, Dillman, and psychometric best practices.
Input
Collect the following from the user before starting. If any required field is missing, ask for it.
Required:
- Research purpose — What research question does this questionnaire answer?
- Target construct — What are you measuring? (one or more constructs)
- Target population — Who will fill out this questionnaire?
- Language — Questionnaire language (default: same as conversation language)
Optional:
- Existing theory or model
- Expected sub-dimensions
- Item count limit
- Special needs (cross-cultural, specific population, etc.)
Process
The workflow has two phases: an alignment phase (interactive) and an execution phase (autonomous).
Phase 1: Align — Construct Definition (interactive)
This is the only phase that requires user confirmation. Getting the construct definition and sub-dimensions right is critical because everything downstream depends on it. If this is wrong, the entire questionnaire is wasted effort.
Step 1: Load Reference Frameworks
Read all four reference files:
- COSMIN content validity framework — evaluation criteria for measurement instruments
- Dillman survey design principles — item writing and questionnaire structure rules
- Common pitfalls checklist — defects to actively avoid
- Self-evaluation rubric — scoring rubric for the finished questionnaire
Step 2: Propose Construct Definition
Based on the user's research purpose, present the following to the user for confirmation:
- Operational definition of the construct (cite supporting literature/theory)
- Distinction from related concepts — how it differs from similar constructs
- Existing validated scales — list them, compare, explain why a new instrument is needed (or recommend adopting an existing one if it fits)
- Sub-dimension decomposition with definition and source for each
- Item blueprint — sub-dimension × planned item count
What ships with it
6 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.
- 12d ago First seen · 300 lines · 72 tokens per session scan A 0324bd2668d3
survey-design is a skill published in the GitHub repository unbias38/my-claude-skills (2 stars, last pushed 17d ago), licensed MIT. It adds 72 tokens to every session and 2,884 once invoked, about $0.0004 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-31.
Other skills, from other repositories
stuck
Diagnoses a broken course setup by reading the folder, so the student never has to describe the problem in English. Takes no argument. Reports which class they are on and which files are filled, then names one blocker and one fix: Claude Code opened at the wrong level, .claude/skills/ missing, skills not loading…
interview-kit-builder
Build a complete, structured interview kit for a role — competency-based questions, what good/weak answers look like, a scoring rubric, and a stage plan. Use when the user is preparing to interview candidates, asks for interview questions, needs an interview scorecard, or wants to set up a hiring process for a role.
skill-creation-walkthrough
Step-by-step guide for creating your own Claude Skills, from deciding whether a skill is the right tool to writing the SKILL.md file, structuring reference material, and making it trigger reliably. Use when you want to package a workflow, framework, or repeated task into a reusable Skill, when an existing skill is not…
interactive-product-tour
Designing in-product tours, tooltips, and contextual help that teach product capabilities without becoming friction. Trigger logic, tour architecture, contextual placement, completion tracking. Honest about tooltip-spam (visual noise that users develop blindness to), one-and-done (help invisible at the moment of…
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
onboarding
Guides a first-time omo user through setup and the core workflow. Use when a new user asks to get started with omo.