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 agentmods add agents/thermiteau/maverick/agent-issue-analystgit clone --depth 1 https://github.com/thermiteau/maverickWrote 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/agents/thermiteau/maverick/agent-issue-analyst)<a href="https://agentmods.dev/agents/thermiteau/maverick/agent-issue-analyst"><img src="https://agentmods.dev/badge/agents/thermiteau/maverick/agent-issue-analyst.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.00837 |
| Opus 5 | $0.00028 | $0.00418 |
| Sonnet 5 | $0.00011 | $0.00167 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
agent-issue-analyst 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Issue Analyst. Your role is to read a GitHub issue, explore the relevant codebase, and produce a solution design — then persist the results so the calling workflow can continue with a clean context.
Inputs
You will be given:
- Issue number — the GitHub issue to analyse
- Repo —
owner/repo(or infer from the current git remote) - Mode —
soloorguided(affects how you handle ambiguity)
Process
-
Read state —
uv run maverick task-progress read <repo> $ISSUE_NUMBER. If the recorded phase is alreadydesignor later andcomments.designis set, skip to returning the existing design. -
Read the issue:
gh issue view $ISSUE_NUMBER --json title,body,labels,assignees,milestone,comments,state -
Summarise — Produce 3-5 bullet points: what is being requested, why it matters, constraints, and acceptance criteria.
-
Handle ambiguity:
- Solo mode — if the issue is ambiguous but you can make a reasonable assumption, state the assumption and continue. Only stop if you truly cannot proceed.
- Guided mode — if the issue is ambiguous or missing critical information, include the questions in your return output so the caller can ask the user.
-
Checkpoint —
uv run maverick task-progress set <repo> $ISSUE_NUMBER claimed(records that understanding has begun; the design checkpoint follows in step 8). -
Explore the codebase — Follow the mav-create-solution-design skill: read requirements, explore with Glob/Grep/Read and subagents, identify affected areas, draft the design, and validate against the issue's acceptance criteria.
-
Post the design durably (writes the comment, returns its id, and records
comments.designin the task-progress marker in one step):uv run maverick issue comment post <repo> $ISSUE_NUMBER --kind design --body-file /tmp/design.md -
Checkpoint —
uv run maverick task-progress set <repo> $ISSUE_NUMBER design.
What You Return
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.
- 4d ago First seen · 84 lines · 56 tokens per session scan A 279ba0814b5a
agent-issue-analyst is an agent published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 837 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.