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 ReinaMacCredy/maestro --skill maestro-questionnairegit clone --depth 1 https://github.com/ReinaMacCredy/maestroWrote 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/reinamaccredy/maestro/maestro-questionnaire)<a href="https://agentmods.dev/skills/reinamaccredy/maestro/maestro-questionnaire"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-questionnaire/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/reinamaccredy/maestro/maestro-questionnaire"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-questionnaire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Anti-Refusal · line 17 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00056 | $0.00879 |
| Opus 5.5 | $0.00022 | $0.00352 |
| Sonnet 5.5 | $0.00011 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
maestro-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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maestro-questionnaire
Turn something the user cannot answer alone into a questionnaire: a Markdown document they hand to one person to fill in async, or fill out together over a meeting. The recipient holds knowledge the user lacks; the questionnaire pulls it out of them. Read-only toward code; any tier may use it.
Grill the send, not the subject. Interview the user only about the send, which they can always answer: who it goes to, and what they need back. The questions in the document then target the gap between what the recipient knows and what the user needs.
-
Who is it going to? Ask, in one exchange, the recipient's role, expertise, and relationship to the user. This fixes the questionnaire's tone and how much context it must carry. Done when you know who the recipient is and what they know that the user does not.
-
What do you need back? Ask, in one exchange, the specific decisions or facts the user cannot resolve alone and needs from this person. Done when you have a concrete list of what the user must walk away able to do or decide.
-
Write the questionnaire. Draft questions aimed at the gap from steps 1 and 2, following the Document structure below. When an active bundle owns the decision, write it to
.maestro/bundle/<bundle-id>/QUESTIONNAIRE-<slug>.md, record the wait asmaestro work note <id> "blocked: questionnaire <slug> sent to <role>", and set the bundle's NOTES.md Next Action to the return of the answers; otherwise writequestionnaire-<slug>.mdin the current directory. Report the path. Done when the file exists and every item the user named in step 2 is covered by a question.
When the answers come back, they are settled forks: record each as
maestro decision draft "<answer>" --rationale "<why, per <recipient>>" --work <id>
then maestro decision lock <id>, and clear the Next Action. The filled
questionnaire is the evidence the decision cites.
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.
- 1mo ago Changed · +22 tokens per session eaaf9fc690bf
- 1mo ago Changed · +1 lines · -11 tokens per session 182a2ae7acfe
- 1mo ago First seen · 92 lines · 45 tokens per session scan A e3f5f10935fb
maestro-questionnaire is a skill published in the GitHub repository ReinaMacCredy/maestro (235 stars, last pushed 9d ago), licensed MIT. It adds 56 tokens to every session and 879 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
qveris
Access third-party professional data and tools through QVeris: find services, review supported scope when needed, call them, and generate production REST code. Use when existing tools are insufficient, a provider is unknown, comparison or fallback is needed, or the user requests QVeris.
qveris-professional-data
Find and retrieve current professional data through the connected QVeris connector. Use when the user needs structured external data, provider discovery, contract inspection, parameter validation, or an explicitly requested QVeris data call.
lightcad
Use when building or extending a desktop CAD/BIM application with the open-source FeiYang LightCAD platform — plugin development, custom elements, DWG/DXF I/O, 2D drafting and 3D/BIM modeling on C#/.NET. LightCAD (FeiYang Integrated Design Platform) is a C# CAD system integrating 2D design, 3D design, and BIM.
deepseek-harness
Use when building AI agent applications with a plugin-based architecture — Web UI, CLI, Python SDK, Cordis plugin system, multi-model orchestration. DeepSeek Harness (dsh): open-source agent harness by DeepSeek AI where everything is a plugin, powered by Cordis for spatiotemporal composability.
ui5-typescript-conversion
A skill for converting UI5 (SAPUI5/OpenUI5) projects to TypeScript.
skill-creator
Create, edit, improve, or audit AgentSkills. Use when creating a new skill from scratch or when asked to improve, review, audit, tidy up, or clean up an existing skill or SKILL.md file. Also use when editing or restructuring a skill directory (moving files to references/ or scripts/, removing stale content, validating…