gitlab-sprint

A set of commands for managing GitLab sprints, which are planned periods of work tracked with milestones and issues. It can also create a wiki page for sprint notes and review.

In plain words
What is it for?
Use it to create a sprint milestone, add backlog issues to it, list work by status, track progress, and close the sprint.
Why use it?
It keeps sprint goals, tasks, labels, due dates, and progress together in GitLab. This reduces manual setup and makes it easier to see which sprint issues remain.

Command

Install

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.

agentmods
npx agentmods add commands/gettalon/talon-plugins/gitlab-sprint
Clone the repo
git clone --depth 1 https://github.com/gettalon/talon-plugins
Per session 44 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 898 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00044 $0.00898
Opus 5 $0.00022 $0.00449
Sonnet 5 $0.00009 $0.00180
Haiku 4.5 $0.00004 $0.00090

Measured 2d ago against content hash e71d1dcc332c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gitlab-sprint 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.

plugins/talon/commands/gitlab-sprint.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

GitLab Sprint Management

Create, plan, and manage sprints using GitLab milestones.

Sprint Planning

When the user asks to plan a sprint:

  1. Get project path (required for milestones):
PROJECT_SLUG=$(git remote get-url origin | sed -E 's|.*://[^/]+/||;s|\.git$||')
  1. Create the sprint milestone:
glab milestone create --project "$PROJECT_SLUG" \
  --title "Sprint YYYY-WNN" \
  --description "Sprint goals:\n- Goal 1\n- Goal 2" \
  --due-date "YYYY-MM-DD"
  1. Create sprint issues with milestone:
glab issue create --title "Task title" \
  --description "Description" \
  --label "To Do" \
  --milestone "Sprint YYYY-WNN"
  1. Create sprint wiki page for notes/retrospective:
PROJECT_PATH=$(echo "$PROJECT_SLUG" | sed 's|/|%2F|g')
glab api "projects/${PROJECT_PATH}/wikis" --method POST \
  --field "title=Sprint-YYYY-WNN" \
  --field "content=# Sprint YYYY-WNN\n\n## Goals\n- [ ] Goal 1\n\n## Notes\n\n## Retrospective\n"

Sprint Progress

# All sprint issues
glab issue list --milestone "Sprint YYYY-WNN"

# Sprint issues by status
glab issue list --milestone "Sprint YYYY-WNN" --label "To Do"
glab issue list --milestone "Sprint YYYY-WNN" --label "Doing"
glab issue list --milestone "Sprint YYYY-WNN" --label "Done"

# Count (via API)
PROJECT_PATH=$(git remote get-url origin | sed -E 's|.*://[^/]+/||;s|\.git$||' | sed 's|/|%2F|g')
glab api "projects/${PROJECT_PATH}/milestones?title=Sprint+YYYY-WNN" | python3 -c "
import sys,json
ms = json.load(sys.stdin)
if ms:
    m = ms[0]
    print(f'Sprint: {m[\"title\"]}')
    print(f'Due: {m.get(\"due_date\",\"not set\")}')
    print(f'State: {m[\"state\"]}')
"

Close Sprint

# Close all done issues
glab issue list --milestone "Sprint YYYY-WNN" --label "Done" | grep '#' | awk '{print $1}' | sed 's/#//' | while read id; do
  glab issue close "$id"
done

# Close milestone
PROJECT_PATH=$(git remote get-url origin | sed -E 's|.*://[^/]+/||;s|\.git$||' | sed 's|/|%2F|g')
MILESTONE_ID=$(glab api "projects/${PROJECT_PATH}/milestones?title=Sprint+YYYY-WNN" | python3 -c "import sys,json; ms=json.load(sys.stdin); print(ms[0]['id'] if ms else '')")
glab api "projects/${PROJECT_PATH}/milestones/${MILESTONE_ID}" --method PUT --field "state_event=close"

# Move unfinished issues to next sprint
glab issue list --milestone "Sprint YYYY-WNN" --opened | grep '#' | awk '{print $1}' | sed 's/#//' | while read id; do
  glab issue update "$id" --milestone "Sprint YYYY-WNN+1"
done

Read the full file on GitHub · 90 lines

Changes

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.

  1. 2d ago First seen · 90 lines · 44 tokens per session scan A e71d1dcc332c

Subscribe to this mod's changes

gitlab-sprint is a command published in the GitHub repository gettalon/talon-plugins (6 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 898 once invoked, about $0.0002 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-31.