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 perf-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/perf-check)<a href="https://agentmods.dev/skills/josstei/maestro-orchestrate/perf-check"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/perf-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/perf-check"><img src="https://agentmods.dev/badge/skills/josstei/maestro-orchestrate/perf-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.00018 | $0.00172 |
| Opus 5.5 | $0.00007 | $0.00069 |
| Sonnet 5.5 | $0.00004 | $0.00034 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
perf-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 Perf Check
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 performance target or pain point
- Establish the current baseline from available code, metrics, or reproducible commands
- Identify likely hotspots, structural bottlenecks, and hot loops through code analysis
- Prioritize fixes by expected impact versus implementation cost
- Report measurement gaps when hard evidence is unavailable and propose a validation plan
Constraints
- Avoid optimization advice that is disconnected from the observed bottleneck
- Distinguish measured issues from inferred ones
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 · 18 tokens per session scan A 7a2ce9c15daa
perf-check is a skill published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 172 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
autofix
Review and repair current local changes until they converge, or run Qwen Code Autofix issue and review workflows from GitHub Actions.
superlint
This skill describes the mandatory standard operating procedure for using our internal SuperLint tool. Use this when tasks require fixing code quality issues according to corporate standards.
second-opinion
Get an independent review of the current change from a different model family (GPT via Codex, Copilot or Cursor; Gemini via Antigravity) through agent-intern, then check each finding against the code and reconcile it with your own view. Use before merging a risky diff, when stuck on a bug, or when the user asks for a…
code-review-checklist
Structured checklist for code review: bugs, style, performance, security, docs.
wcode
Use the wcode plugin and its MCP tools for repository coding, review, debugging, refactoring, architecture, Graph/Design inspection, safe edits, command execution, and verification. Trigger whenever wcode is installed or named, even when its tools are lazily registered or omitted from the host's initial tool list.
band-aid-finder
Finds fixes that hide a symptom instead of fixing the cause, traces each to its root cause, and proposes the real fix. Allows deliberate, documented mitigations. Trigger on: "is this a real fix or a band-aid", "am I treating the symptom", "why does this keep happening", "find the root cause".