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 security-auditgit 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/security-audit)<a href="https://agentmods.dev/skills/josstei/maestro-orchestrate/security-audit"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/security-audit/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/security-audit"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/security-audit.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.00210 |
| Opus 5.5 | $0.00010 | $0.00084 |
| Sonnet 5.5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
security-audit 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 3d 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 Security Audit
Call get_skill_content with resources: ["architecture"].
Protocol
Before delegating, call get_skill_content with resources: ["delegation"] and follow the returned methodology.
Workflow
- Define the audit scope from the user request and relevant code paths
- Trace trust boundaries, auth flows, secret handling, and data exposure paths
- Review for exploitable flaws, unsafe defaults, OWASP Top 10 vulnerabilities, and high-risk dependencies
- Classify findings by severity (CVSS-aligned) with file references and exploitability assessment
- Provide remediation guidance with the highest-risk issues first
Constraints
- Prefer actionable findings over generic security advice
- Present findings before proposing remediation
- State clearly when the review is limited by unavailable runtime context
- 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.
- 3d ago First seen · 29 lines · 25 tokens per session scan A 70f740293b5a
security-audit is a skill published in the GitHub repository josstei/maestro-orchestrate (465 stars, last pushed 3d ago), licensed Apache-2.0. It adds 25 tokens to every session and 210 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
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.
chisle-review
Review a diff or file through the Chisle lens: flag over-engineering, speculative abstractions, reinvented stdlib, and verbose code that a lazier approach would shrink. One finding per line, no praise. Use when the user says "chisle review", "review this for bloat", or invokes /chisle-review.
chisle-help
Quick-reference card for Chisle commands. One-shot display, not a persistent mode. Use when the user says "chisle help", "how do I use chisle", "what chisle commands", or invokes /chisle-help.
install-gemini-code-review-action
Installs, configures, or upgrades Dazbo's PR code review & issue triage GitHub Action (gemini-review-action) in a target repository. Use when the user wants to set up, configure, or update automated AI code reviews, issue triaging, or Gemini model workflows for their GitHub repository.
comment-reaper
Finds and removes unnecessary code comments - the ones that restate the code, cite an issue number, narrate refactor history, or wrap a one-line function in six lines of JSDoc. Sorts every find into auto-fix, propose, or never-touch, so the WHY comments survive the sweep. Trigger on: "comment reaper", "reap comments"…
codeck
Keep Codex as the host. Use Codeck when the user explicitly asks to call Agy/AGY, Antigravity, Gemini, Claude, Kimi, Grok, Codeck, or another configured external executor. These names mean external Codeck executors, never internal Codex subagents. Build a compact task-specific brief, call that specialist, and return…