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 aethrox/doctrine --skill to-questionnairegit clone --depth 1 https://github.com/aethrox/doctrineWrote 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/aethrox/doctrine/to-questionnaire)<a href="https://agentmods.dev/skills/aethrox/doctrine/to-questionnaire"><img src="https://agentmods.dev/badge/skills/aethrox/doctrine/to-questionnaire.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.00060 | $0.01001 |
| Opus 5 | $0.00030 | $0.00500 |
| Sonnet 5 | $0.00012 | $0.00200 |
| Haiku 4.5 | $0.00006 | $0.00100 |
Grade A, and why
to-questionnaire 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 8d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Questionnaire
A questionnaire only earns its place when the knowledge gap is real and the recipient is the only one who can close it; this skill's defining constraint is that every question in the document targets that gap specifically, grounded in established survey-design practice: neutral, unbiased phrasing (never a leading or loaded question), the right choice between closed and open questions for what's actually being asked, and a correctly-balanced scale wherever a rating is needed.
Interview the person sending the questionnaire only about the send (who it's going to and what's needed back), never about the subject itself, since the subject is exactly what the recipient knows and the sender doesn't.
Phase 1: Scope the send
Establish two things before drafting a single question:
- Who's the recipient: their role, expertise, and relationship to the sender. This fixes the questionnaire's tone and how much background context it needs to carry; a peer needs less framing than someone outside the team entirely.
- What's actually needed back: the specific decisions or facts the sender can't resolve alone. A vague goal ("get their thoughts") produces a vague questionnaire; a concrete list of what the sender must walk away able to decide produces a targeted one.
Phase 2: Choose closed or open per question, deliberately
Neither is a default; each question earns its format from what it's actually collecting:
- Closed (multiple choice, yes/no, a scale) when the answer needs to be quick, comparable across respondents, or clearly structured: at the cost of not capturing anything outside the offered options.
- Open when the sender needs context, reasoning, or an answer that can't be enumerated in advance: at the cost of being harder to compare or aggregate later.
Pairing a closed question with a short open follow-up ("why?") is often the right shape when both the fact and the reasoning behind it matter.
Phase 3: Write every question to avoid leading and loading
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.
- 8d ago First seen · 53 lines · 60 tokens per session scan A 29b44f8c7a57
to-questionnaire is a skill published in the GitHub repository aethrox/doctrine (18 stars, last pushed 27d ago), licensed MIT. It adds 60 tokens to every session and 1,001 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
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, then fills the gaps with list (filters, sort, a time…
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.