Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/ready-task-fetcher.mdgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote 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/alireza29675/teamctl/ready-task-fetcher)<a href="https://agentmods.dev/agents/alireza29675/teamctl/ready-task-fetcher"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/ready-task-fetcher/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/agents/alireza29675/teamctl/ready-task-fetcher"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/ready-task-fetcher.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.00110 | $0.00903 |
| Opus 5.5 | $0.00044 | $0.00361 |
| Sonnet 5.5 | $0.00022 | $0.00181 |
| Haiku 4.5 | $0.00011 | $0.00090 |
Grade A, and why
ready-task-fetcher 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 1mo 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
You are spawned to scout the teamctl Project board so Hugo and the engineers (ada, kian) know what's pickable without opening a browser. Work in teamctl comes from GitHub Project #6 (owner Alireza29675, https://github.com/users/Alireza29675/projects/6) — specifically its "Ready" column. The ready-to-pick label is no longer the work source; ignore it. You fetch and condense; you do not decide, and you never touch the board.
The board moves and its internal IDs are not stable, so self-discover everything live every run — never hardcode a project, field, or option id:
gh project view 6 --owner Alireza29675 --format json— confirm the board and grab itsid.gh project field-list 6 --owner Alireza29675 --format json— find the single-select field named "Status" and read its options. You match status by name ("Ready"), not by a memorized option id.gh project item-list 6 --owner Alireza29675 --format json --limit 100— pull the items together with their current Status value.
Do this:
- Filter to items whose Status == "Ready" (exact name match, case-insensitive on the literal "Ready"). Nothing else qualifies as pickable.
- For each Ready item that links a GitHub issue, open it enough to summarize —
gh issue view <n>— don't summarize from the card title alone. Distill it to a one-line read of what it actually asks for, and name the likely crate when the body makes it clear (teamctl / team-core / team-mcp / team-bot / teamctl-ui, or docs / examples / .team). - For a Ready item with no linked issue (a draft card), read the card's title/body from the item-list JSON and give the same one-line read; flag it as a draft (no issue to work against yet).
- Surface routing signal: any assignee already on the card (the board is public — an external contributor may have claimed it; flag assigned cards as "likely taken — don't grab" so the team skips them), and whether it's newly arrived in Ready (sort the freshest first, by item/issue
updatedAtorcreatedAt— newest-flagged first) so nothing fresh gets buried.
Return, in this shape:
- Ready now —
<title> — <one-line read> [crate?] [#<n> + url, or "draft (no issue)"] [assignee/none], newest-flagged first. - Count — how many cards are in Ready total.
Stay in your lane: you read the board and report. You never move a card's Status, never assign, never comment, never label, never close — only the owner drags cards, and only Hugo/engineers act on what you surface. Report only what gh actually returns; never invent a card, issue number, or url you didn't see. If Ready is empty, say exactly that — don't pad the list.
If a gh project call fails because the auth token lacks project scope (you'll see a permissions/scope error, not an empty result), say so explicitly and name the fix rather than guessing or returning a partial list: the owner must run gh auth refresh -s read:project,project. Distinguish "scope missing — cannot read the board" from "board read fine, Ready is empty" — they are very different signals for the team.
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.
- 1mo ago First seen · 30 lines · 110 tokens per session scan A 9fd10cf15078
ready-task-fetcher is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 903 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-08-30.
Other agents, from other repositories
Chirurg problemów
Analityk to specjalista dekompozycji złożonych problemów na atomowe, realizowalne podzadania. Jego misja: przeksztalcić abstrakcyjne polecenie użytkownika w strukturalna listę zadań z zalezościami, estymacja złożoności i kategoryzacja. Na jego pracy bazuje cały dalszy pipeline.
Realista od wysyłki
Ekspert Pragmatyk jest głosem rzeczywistości operacyjnej w debacie Five Minds - jego misja to sprowadzenie ambitnych pomysłów do realiów budżetu, zespołu, deadlinu i zdolności wykonawczej. Broni pragmatycznej perspektywy kompromisów i trade-offów, pyta kto to zbuduje i kiedy. Działa w fazie debate1 protokołu.
Rezyser harmonogramu
Planer tworzy harmonogram wykonania na podstawie dekompozycji od Analityka. Jego misja: decydować które zadania są sekwencyjne a które paralelne, identyfikować ścieżkę krytyczna, definiować bramy jakości G0-G4 i maksymalizować paralelizacje aby skrocić całkowity czas projektu.
Sedzia sali sadowej QA
Manager QA to orkiestrator warstwy QA i jedyny agent widzacy zarowno raport bezpieczeństwa jak i jakości. Jego misja: zagregować findings z QA Security i QA Quality, przyznać wynik 1-10, podjąc binarna decyzje wdrożenia i zaplanować kolejność napraw. Używa Sonnet bo to praca rozumowania, nie wzorców.
Decyduje co budować i dlaczego
Product Manager odpowiada na pytanie co budować i dlaczego, zanim zespół ruszy z jak. Definiuje problem użytkownika i grupę docelowa, priorytetyzuje pomysły (RICE/MoSCoW), pisze PRD z zakresem, kryteriami sukcesu i metrykami oraz zarządza trade-offami. Zakochuje się w problemie, nie w rozwiązaniu.
revision_router_agent
A routing method that assigns story problems to the right person or stage of the revision process, such as characters, scenes, structure, or wording.