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.
git clone --depth 1 https://github.com/gettalon/talon-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/commands/gettalon/talon-plugins/gitlab-board)<a href="https://agentmods.dev/commands/gettalon/talon-plugins/gitlab-board"><img src="https://agentmods.dev/badge/commands/gettalon/talon-plugins/gitlab-board/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/commands/gettalon/talon-plugins/gitlab-board"><img src="https://agentmods.dev/badge/commands/gettalon/talon-plugins/gitlab-board.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.00035 | $0.00838 |
| Opus 5.5 | $0.00014 | $0.00335 |
| Sonnet 5.5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
gitlab-board 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Board Management
Create and manage issue boards via glab api.
Setup Board
Boards use glab api (no native CLI). Always get the project path first:
PROJECT_PATH=$(git remote get-url origin | sed -E 's|.*://[^/]+/||;s|\.git$||' | sed 's|/|%2F|g')
Create Scrum Labels
glab label create --name "To Do" --color "#F0AD4E" --description "Backlog / ready for work"
glab label create --name "Doing" --color "#5CB85C" --description "In progress"
glab label create --name "Review" --color "#0033CC" --description "In code review"
glab label create --name "Done" --color "#69D100" --description "Completed"
Create Board
glab api "projects/${PROJECT_PATH}/boards" --method POST --field "name=Scrum Board"
Add Label Columns to Board
Get label IDs first:
glab label list
Then add each label as a board list:
BOARD_ID=<from board creation>
glab api "projects/${PROJECT_PATH}/boards/${BOARD_ID}/lists" --method POST --field "label_id=<TO_DO_ID>"
glab api "projects/${PROJECT_PATH}/boards/${BOARD_ID}/lists" --method POST --field "label_id=<DOING_ID>"
glab api "projects/${PROJECT_PATH}/boards/${BOARD_ID}/lists" --method POST --field "label_id=<REVIEW_ID>"
glab api "projects/${PROJECT_PATH}/boards/${BOARD_ID}/lists" --method POST --field "label_id=<DONE_ID>"
View Board
# List boards
glab api "projects/${PROJECT_PATH}/boards" | python3 -c "
import sys,json
for b in json.load(sys.stdin):
print(f'Board: {b[\"name\"]} (ID: {b[\"id\"]})')
for l in b.get('lists',[]):
label = l.get('label',{})
print(f' [{l[\"position\"]}] {label.get(\"name\",\"?\")} (list_id: {l[\"id\"]})')
"
# View board in browser
glab repo view --web # then navigate to Issues > Boards
Move Issues on Board
Moving an issue between columns = swapping labels:
# To Do → Doing
glab issue update <ID> --label "Doing" --unlabel "To Do"
# Doing → Review
glab issue update <ID> --label "Review" --unlabel "Doing"
# Review → Done
glab issue update <ID> --label "Done" --unlabel "Review"
glab issue close <ID>
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 · 96 lines · 35 tokens per session scan A b9d69a2191cd
gitlab-board is a command published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 838 once invoked, about $0.0001 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-31.
Other commands, from other repositories
qa
Dispatch a verifiable browser task to the qa-tester subagent. Use for regression checks, smoke tests, and any task with a clean pass/fail outcome. Supports an EXHAUSTIVE mode that verifies every control behind an honesty gate.
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
design-qa
Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
review-session
Arm-2 — critique the current/last session for efficiency & quality, emit a Zone-A distillation, offer a deliberate GitHub feedback report.
feedback
File a plugin-capability-gap note, or flush queued notes to GitHub issues.