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 matthewdigiuseppe/MStack/plugin install mstackWrote 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/matthewdigiuseppe/mstack/survey-build)<a href="https://agentmods.dev/skills/matthewdigiuseppe/mstack/survey-build"><img src="https://agentmods.dev/badge/skills/matthewdigiuseppe/mstack/survey-build.svg" alt="Measured on agentmods" 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.00064 | $0.00942 |
| Opus 5 | $0.00032 | $0.00471 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
survey-build 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 6d 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.
/mstack:survey-build
Stage: design Voice: survey-designer
When to invoke
You're designing a new survey instrument — a survey experiment, a panel, or a benchmark study comparing humans and AI agents. Run before programming the Qualtrics flow, not after.
Procedure
-
Establish the science target.
- Read
.mstack/config.yamlfor paper context. - Ask (or read prior context for) the four design questions:
- Population and sample frame.
- Treatment(s) — what is randomized, when, by whom.
- Outcome(s) — primary, secondary, manipulation checks.
- Inference unit — individual, dyad, time-series.
- Record the answers in
.mstack/survey-design.md.
- Read
-
Layer in the bot/agent defenses.
- Use the agent-disclosure skill if the user has it installed; otherwise follow
${CLAUDE_PLUGIN_ROOT}/references/survey-bot-defenses.md. Either way, layer in:- Attention checks calibrated to expected human reading time.
- Behavioral probes (timing distributions, paste-detection, mouse-tracking opt-ins).
- Instructional manipulation checks.
- Open-ended response quality checks.
- Exclusion rules with thresholds.
- This is non-optional. Every MStack survey ships with a probe manifest.
- Use the agent-disclosure skill if the user has it installed; otherwise follow
-
Draft the instrument. Produce, in
.mstack/survey-design.md:- Block plan with conditional logic.
- Question table — for each question: ID, type, wording, response options, required y/n, randomization rules, branching.
- Embedded data fields — treatment assignment, condition labels, timing variables, IP-region (if collected).
- Probe manifest (from agent-disclosure): each probe with its trigger condition, scoring rule, and exclusion threshold.
- Webhooks/quotas — if balancing on demographics, document quota logic.
-
Hand off to Qualtrics.
- If the user has a Qualtrics MCP connected, offer to programmatically create the survey, blocks, and questions.
- Otherwise produce a copy-paste-ready spec the user can build manually.
- Either way, save the spec to
.mstack/survey-design.mdso the design is reproducible.
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.
- 6d ago First seen · 77 lines · 64 tokens per session scan A d0f197422d6e
survey-build is a skill published in the GitHub repository matthewdigiuseppe/MStack (14 stars, last pushed 9d ago), licensed MIT. It adds 64 tokens to every session and 942 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…