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 23blocks-OS/ai-maestro-plugins --skill agent-tasksgit clone --depth 1 https://github.com/23blocks-OS/ai-maestro-pluginsWrote 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/23blocks-os/ai-maestro-plugins/agent-tasks)<a href="https://agentmods.dev/skills/23blocks-os/ai-maestro-plugins/agent-tasks"><img src="https://agentmods.dev/badge/skills/23blocks-os/ai-maestro-plugins/agent-tasks/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/23blocks-os/ai-maestro-plugins/agent-tasks"><img src="https://agentmods.dev/badge/skills/23blocks-os/ai-maestro-plugins/agent-tasks.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.00109 | $0.00911 |
| Opus 5.5 | $0.00044 | $0.00364 |
| Sonnet 5.5 | $0.00022 | $0.00182 |
| Haiku 4.5 | $0.00011 | $0.00091 |
Grade A, and why
agent-tasks 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 today.
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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent tasks
The operator opens a Board tab for each agent: columns To Do, In Progress, Review, Waiting, Done. A card you do not move is a card that lies. Keep it true with aimaestro-task.sh; it works on your own board, on this host.
aimaestro-task.sh add "Ship the consent banner" [--desc "..."] # you took a task on
aimaestro-task.sh start <id> # you began working on it
aimaestro-task.sh review <id> # it is waiting for someone to check it
aimaestro-task.sh done <id> # finished
aimaestro-task.sh wait <id> --on juan --note "needs the final copy"
aimaestro-task.sh comment <id> "what you did, or what you need"
aimaestro-task.sh place <id> q1 # q1 do first, q2 schedule, q3 delegate, q4 delete (none: take it off)
aimaestro-task.sh list # your board (--quadrant q1 shows one square)
aimaestro-task.sh show <id> # one card with its comments
<id> is the full id or the first characters shown by list and in [TASK d773ef06].
When to move a card
- A task is assigned or you pick one up:
add(thenstartwhen you begin). - You stop because you need something:
waitand say on whom:juan(the operator),outside(someone not on AI Maestro),hold(paused on purpose, nobody is blocking it), or another agent's id. Say what exactly in--note; it is the first thing the operator reads.startagain when the wait is over. - The work is done and someone should look:
review. Done and nothing more to do:done. - Use
commentfor context about a task instead of sending a new message about it. Your comments stay on the card and are shown; they are not sent to anyone's prompt.
The matrix
The operator also sees every card on an Eisenhower matrix: q1 urgent and important (do first), q2 important, not urgent (schedule), q3 urgent, not important (delegate), q4 neither (delete). Place a card when you add it (add "..." --quadrant q1, or place <id> q2 later) and move it when the deadline or the owner changes. A card you did not place sits in "Not placed", which is not the same as q4.
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.
- today First seen · 53 lines · 109 tokens per session scan A bf153f448298
agent-tasks is a skill published in the GitHub repository 23blocks-OS/ai-maestro-plugins (11 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 911 once invoked, about $0.0004 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-20.
Other skills, from other repositories
task-coordination
Patterns for using TaskCreate, TaskUpdate, TaskList, and TaskGet to coordinate multi-step work. Use when the user has a complex project with multiple steps, needs progress tracking, dependency management, or multi-agent task assignment.
project_state_management
Maintain clear project context and avoid hallucinations using GSD State Files.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…