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 josstei/maestro-orchestrate --skill compliance-checkgit clone --depth 1 https://github.com/josstei/maestro-orchestrateWrote 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/josstei/maestro-orchestrate/compliance-check)<a href="https://agentmods.dev/skills/josstei/maestro-orchestrate/compliance-check"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/compliance-check/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/josstei/maestro-orchestrate/compliance-check"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/compliance-check.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.00025 | $0.00184 |
| Opus 5.5 | $0.00010 | $0.00074 |
| Sonnet 5.5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
compliance-check 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.
What it actually says
Maestro Compliance Check
Call get_skill_content with resources: ["architecture"].
Protocol
Before delegating, call get_skill_content with resources: ["delegation"] and follow the returned methodology.
Workflow
- Identify applicable regulations and define audit scope
- Review data handling patterns, user disclosures, consent flows, retention policies, and third-party integrations
- Audit regulatory compliance: GDPR/CCPA, cookie consent, data residency, licensing, and open-source obligations
- Present findings with regulatory reference, severity, compliance risk, and recommended actions
- Distinguish legal-risk observations from code-level bugs
Constraints
- Present findings before proposing remediation
- Do not modify code without explicit user approval
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 · 27 lines · 25 tokens per session scan A dd522d07bf6b
compliance-check is a skill published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 5d ago), licensed Apache-2.0. It adds 25 tokens to every session and 184 once invoked, about $0.0001 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-10-07.
Other skills, from other repositories
audit-expert
Expert-level security auditing, compliance, code review, and vulnerability assessment. Use when the user mentions compliance, security review, code review, vulnerability assessment, SOC 2, or GDPR, or when the task involves Audit Types, Audit Frameworks, Audit Process, or Authentication Review.
code-review-php
Deep PHP-specific code review covering strict types, PHPStan compliance, PSR standards, domain modeling, and ORM boundary violations. Applied in addition to the generic code-review skill when PHP code is detected. Invoked when reviewing PHP PRs, Symfony/Laravel changes, or performing PHP-specific quality checks.
ruthless-refactorer
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
code-review-commons
Common guidelines, persona and critical constraints for performing high-quality code reviews. Use this skill when performing a /code-review or /pr-code-review command.
code-review
Perform thorough code review and audit of implemented features. Compares implementation against the technical plan, checks for AI-specific risks, and provides actionable feedback. Activate for: review, audit, code quality assessment, security review.
symbi-audit
Query and analyze Symbiont's cryptographic audit logs. Use when reviewing agent activity, investigating incidents, or preparing compliance reports.