Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tinhtran24/maestronpx agentmods add skills/tinhtran24/maestro/bug-triageWrote 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/tinhtran24/maestro/bug-triage)<a href="https://agentmods.dev/skills/tinhtran24/maestro/bug-triage"><img src="https://agentmods.dev/badge/skills/tinhtran24/maestro/bug-triage/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/tinhtran24/maestro/bug-triage"><img src="https://agentmods.dev/badge/skills/tinhtran24/maestro/bug-triage.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.00033 | $0.04720 |
| Opus 5 | $0.00016 | $0.02360 |
| Sonnet 5 | $0.00007 | $0.00944 |
| Haiku 4.5 | $0.00003 | $0.00472 |
Grade A, and why
bug-triage 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 9d 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage Skill
Triage bugs into well-structured GitHub issues on the upstream AgentWrapper/maestro repo (issues are enabled there; the origin fork is not the issue tracker).
Maestro is Go + Electron. The backend is a Go daemon (
backend/) exposing a loopback HTTP API on127.0.0.1:3001; the frontend is an Electron + React supervisor (frontend/). There is no pm2/tmux-per-session Node runtime here: the daemon owns lifecycle and terminals run under the tmux runtime adapter (ConPTY on Windows). Triage against this Go rewrite, not the old TypeScript maestro implementation.
⚠️ Which maestro are you running?
A bare maestro on your PATH may resolve to a different Maestro install (for example an
old npm build at ~/.nvm/.../bin/to that talks to port :3000). Triaging with
the wrong binary produces bugs that don't exist in this rewrite (and misses ones
that do).
Before any diagnostics:
which -a to # see every to on PATH; expect surprises
maestro status 2>/dev/null # if this shows port 3000, it is NOT this rewrite
Use a rewrite binary explicitly:
# Option A: build from this repo (preferred during triage)
cd backend && go build -o /tmp/to ./cmd/maestro
/tmp/to status # must report port: 3001
# Option B: the packaged app's bundled daemon
"/Applications/Maestro.app/Contents/Resources/daemon/to" status
Confirm maestro status reports port: 3001 before trusting any output. Throughout
this skill, maestro means your verified rewrite binary (/tmp/to or the bundled
one), never a bare PATH lookup.
Note: spawned sessions get a PATH pin so the session's
maestroresolves to the daemon's own executable (seehookPATHinbackend/internal/session_manager/manager.go). That pin only applies inside sessions; your interactive shell is still on its own PATH, so pin it yourself.
1. Pre-flight
- Pull latest code:
git fetch upstream && git log --oneline upstream/main -5. Stale code means bad triage. (upstream=AgentWrapper/maestro.) - Target repo: Always file on
AgentWrapper/maestro(the upstream product repo, where issues live). Never file on theoriginfork or ontinhtran/*. - Verify your binary: confirm
maestro statusshows port 3001 (see warning above). - Record source: chat URL, reporter name, attachments.
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.
- 9d ago First seen · 433 lines · 33 tokens per session scan A 5947ce62f8d4
bug-triage is a skill published in the GitHub repository tinhtran24/maestro (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 4,720 once invoked, about $0.0002 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
resolving-merge-conflicts
Use when git merge or rebase fails with conflicts, you see 'unmerged paths' or conflict markers (<<<<<<< =======), or need help resolving conflicted files. Triggers: 'merge conflict', 'fix the conflicts', 'conflicting changes', 'resolve conflicts', 'can't merge'.
manage-skills
A maintenance workflow for checking whether project verification skills still cover the code and rules that changed during a session.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
systematic-debugging
Structured debugging methodology — use before proposing fixes for any error or failure. Covers: code bugs, build errors, deploy failures, config conflicts, dependency issues, infra problems. Also use when previous fix attempts failed or root cause is unclear.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
docs-release-notes
Use when a change needs a user-visible release-note, changelog, or changeset entry — "add a release note", "add a changeset for this", "what goes in the changelog?", "write up what shipped", "note this for the next release" — or when finalizing a branch whose customer-visible features, bug fixes, or UI changes should…