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 bromso/metapowers --skill compliance-questionnairegit clone --depth 1 https://github.com/bromso/metapowersWrote 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/bromso/metapowers/compliance-questionnaire)<a href="https://agentmods.dev/skills/bromso/metapowers/compliance-questionnaire"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-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/bromso/metapowers/compliance-questionnaire"><img src="https://agentmods.dev/badge/skills/bromso/metapowers/compliance-questionnaire.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.00006 | $0.00549 |
| Opus 5 | $0.00003 | $0.00275 |
| Sonnet 5 | $0.00001 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
compliance-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 10d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Questionnaire
Answer customer security and compliance questionnaires for "$ARGUMENTS" by leveraging existing compliance artifacts, evidence, and organizational knowledge to provide accurate, evidence-backed responses.
Prerequisites
None — this is a utility skill.
Process
-
Read context files:
- Read
plugins/compliance/shared/grc-lifecycle-guide.mdfor GRC methodology reference - Read any existing compliance artifacts in
.metapowers/compliance/$ARGUMENTS/for context (if they exist)
- Read
-
Understand the questionnaire:
- Identify questionnaire type — SIG (Standardized Information Gathering), CAIQ (Consensus Assessments Initiative Questionnaire), VSAQ, or custom
- Parse questionnaire structure and question categories
- Identify total number of questions and sections
- Note any specific format requirements for responses
-
Answer each question:
- For each question: determine the most accurate response based on current compliance posture
- Cite existing evidence where available (SOC 2 report, ISO certificate, policies)
- Use standard compliance language appropriate to the questionnaire type
- For yes/no questions: answer honestly, provide brief justification
- For descriptive questions: provide concise, factual responses with evidence references
-
Flag and annotate:
- Flag questions that require internal verification before submission
- Identify answers that might concern the customer — provide mitigation context
- Note questions where the organization is non-compliant — suggest compensating controls or roadmap items
- Mark questions as N/A where genuinely not applicable (with justification)
-
Quality assurance:
- Verify consistency across answers (no contradictions)
- Ensure all questions are addressed (no blanks)
- Check that evidence references are accurate and current
- Review tone — professional, confident, but honest about gaps
-
Write the artifact to
.metapowers/compliance/$ARGUMENTS/questionnaire-responses.mdwith sections:- Questionnaire Summary — type, customer, date, total questions
- Responses — per-section answers in the customer's requested format
- Items Requiring Verification — flagged questions needing internal review
- Customer Concern Areas — potential concerns with mitigation context
- Evidence References — index of all evidence cited in responses
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.
- 10d ago First seen · 58 lines · 6 tokens per session scan A 32914cf986d7
compliance-questionnaire is a skill published in the GitHub repository bromso/metapowers (1 stars, last pushed 4mo ago), licensed MIT. It adds 6 tokens to every session and 549 once invoked, about $0.0000 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
internal-controls-and-audit
Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…
chief-legal-and-risk-officer
Owns legal, contracts, intellectual property, regulatory compliance, privacy, security governance, enterprise risk, and audit readiness. Use this to review a contract or commitment, assess regulatory or privacy exposure, evaluate an IP or licensing question, judge the risk in a business decision, prepare for an audit…
intellectual-property
Covers what the organization owns and what it is only borrowing — trademarks and clearance, copyright and work-for-hire, patents and trade secrets, open-source license obligations and copyleft reach, and IP terms in customer, contractor and AI-tool agreements. Use this to check whether a name is usable, establish that…
chief-human-resources-officer
Owns the organization itself: org design, hiring, performance, compensation, development, culture, and employee relations. Use this to design or restructure a team, plan hiring, write a role or leveling definition, handle a performance or compensation question, diagnose why a team is underperforming for non-technical…
deal-negotiation
Negotiates a commercial deal without giving away the terms that matter — preparing your walk-away and theirs, trading concessions rather than conceding them, recognizing the tactics that create false urgency, protecting price by moving other variables, and closing on terms someone can actually deliver. Use this to…
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…