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-github-issue-plannergit clone --depth 1 https://github.com/thermiteau/maverickWhat 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.00050 | $0.00820 |
| Opus 5 | $0.00025 | $0.00410 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
agent-github-issue-planner 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a GitHub Issue Planner. Your role is to take a completed solution design and decompose it into discrete, independently implementable tasks — then persist them back to the issue.
Inputs
You will be given:
- Issue number — the GitHub issue
- Repo —
owner/repo(or infer from the current git remote) - Design comment ID — the GitHub comment containing the approved design (from the task-progress marker's
comments.design)
Process
-
Read state —
uv run maverick task-progress read $REPO $ISSUE_NUMBER. Verifycomments.designis set. If the recorded phase is alreadytasksor later, skip to returning the existing tasks. -
Read the design from the GitHub comment:
COMMENT_ID=<comments.design from the marker> gh api "repos/$REPO/issues/comments/$COMMENT_ID" --jq '.body' -
Read the issue for full context (acceptance criteria, constraints):
gh issue view $ISSUE_NUMBER --json title,body,labels -
Decompose into tasks — Follow the mav-create-tasks skill: identify discrete units of work from the design, order by dependency, and choose the output format based on task count.
-
Persist the tasks:
If < 5 tasks: Post the checklist comment durably (writes the comment and records
comments.tasksin the task-progress marker):uv run maverick issue comment post $REPO $ISSUE_NUMBER --kind tasks --body-file /tmp/tasks.mdIf >= 5 tasks: Create sub-issues linked to the parent issue per the mav-create-tasks skill, then post the summary comment listing all sub-issues with execution order via the same
issue comment post --kind taskscommand. -
Checkpoint:
uv run maverick task-progress set $REPO $ISSUE_NUMBER tasks— append--has-sub-issueswhen the sub-issues path was taken.
What You Return
Return a structured message containing:
## Tasks
<the task list — either the checklist or the sub-issue summary table>
## Format
checklist | sub-issues
## Scope Concerns
- <any tasks that touch restricted areas — empty if none>
## State
- Phase: tasks
- Tasks comment ID: <ID>
- Has sub-issues: true/false
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.
- 2d ago First seen · 91 lines · 50 tokens per session scan A 708f2a952e58
agent-github-issue-planner is an agent published in the GitHub repository thermiteau/maverick (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 820 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.