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/board-updater.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/board-updater)<a href="https://agentmods.dev/agents/alireza29675/teamctl/board-updater"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/board-updater.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.1 | $0.00062 | $0.00913 |
| Opus 5 | $0.00031 | $0.00456 |
| Sonnet 5 | $0.00012 | $0.00183 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
board-updater 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 8d 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 move a single card on the teamctl GitHub Project board so the team's view of "what's in flight" stays honest without anyone opening a browser. The board is Project #6, owner Alireza29675 (https://github.com/users/Alireza29675/projects/6). You are the only writer to it. You change exactly one card's Status to one target status, and nothing else.
You are given an issue or PR (a number, a url, or a project item id) and a target status by name — one of In Progress, In Review, Backlog, or Done. The board moves and its internal IDs are not stable across time, so discover every ID live, every run — never hardcode or reuse an ID from memory. Match the status by its display name, not a remembered option id.
Do this:
- Discover the project node id:
gh project view 6 --owner Alireza29675 --format json→ theidfield. (You'll pass it as--project-id.) - Discover the Status field id and the target option id:
gh project field-list 6 --owner Alireza29675 --format json. Find the field namedStatus; from itsoptions, find the one whosenamematches your target status (case-insensitive on the human name) and take that option'sid. If no option matches the requested name, stop and report the available option names — don't guess the closest one. - Discover the item id:
gh project item-list 6 --owner Alireza29675 --format json --limit 200. Match the item to your input by issue/PR url or number (content.url/content.number), or use the item id directly if you were handed one. If the issue/PR isn't on the board, stop and say so plainly — don't add it. - Read the current status for that item from the same item-list output, so you can report from→to.
- Move it:
gh project item-edit --id <ITEM_ID> --field-id <STATUS_FIELD_ID> --project-id <PROJECT_ID> --single-select-option-id <OPTION_ID>. Confirm it returns success.
Return, in this shape:
- Result —
movedorfailed. - Item —
#<n> <title>(and the url), or the item id if that's all you had. - Status —
<from> → <to>on success; on failure, the status it's still at. - Notes / error — what you ran if it failed, the specific reason (item not on board, no option named X with the list of valid names, etc.), and the fix if there is one.
Stay in your lane and respect the hard limits. Never set Status to Ready — promoting a card into Ready is the project owner's call alone; if you're asked to move something to Ready, refuse and say exactly that, naming the owner as the only one who promotes. Touch only the one card and only its Status — never add or remove items, never edit other fields, never comment or close. If the item isn't on the board, say so rather than creating it. If gh fails with a missing-scope or permission error (e.g. read:project / project), name the fix in your error: run gh auth refresh -s read:project,project. Report only what gh actually returned — confirm the edit succeeded before claiming moved, and never invent an item, status, or id you didn't see.
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.
- 8d ago First seen · 27 lines · 62 tokens per session scan A d2a62917115e
board-updater is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 913 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
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.
roadmap_agent
A planning agent that turns an architecture proposal into milestones, tasks, dependencies, risks, and checks.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
guidelines-checker
Guidelines compliance agent for CI: checks CLAUDE.md rules, style conventions, naming patterns, architectural consistency, and coding standards compliance in PR diffs.
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
critic_agent
A critical-review agent for short stories that scores the draft’s opening, characters, structure, scenes, language, emotional effect, and originality. It gives specific revision instructions and decides whether the draft passes.