sprint-progress-tracker

sprint-progress-tracker is a skill for Claude Code from o2alexanderfedin/strategic-research-automation-template. It costs 0 tokens per session (2,722 once invoked), scanned A, original, MIT.

A skill for tracking the status of software sprints, which are planned work periods, and their tasks. It examines task lists and project files to report progress, file counts, elapsed time, estimated completion, and bottlenecks.

In plain words
What is it for?
Use it to check sprint status, calculate completion percentages, monitor tasks, estimate finishing times, find delays, and prepare stakeholder updates.
Why use it?
It gives a consistent view of what is pending, underway, or finished, so progress does not have to be estimated manually from scattered project files.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the TodoWrite tool.

Good fit Use it to check sprint status, calculate completion percentages, monitor tasks, estimate finishing times, find delays, and prepare stakeholder updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker
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.

Any agent
npx skills add o2alexanderfedin/strategic-research-automation-template --skill sprint-progress-tracker
Clone the repo
git clone --depth 1 https://github.com/o2alexanderfedin/strategic-research-automation-template

Made for: Claude Code.

Wrote 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.

agentmods badge for sprint-progress-tracker

README.md
[![agentmods](https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker/github.svg)](https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker)
Your own site
<a href="https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker/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.

agentmods 80×15 button for sprint-progress-tracker

Your own site · 80×15
<a href="https://agentmods.dev/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker"><img src="https://agentmods.dev/badge/skills/o2alexanderfedin/strategic-research-automation-template/sprint-progress-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,722 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.02722
Opus 5 $0.00000 $0.01361
Sonnet 5 $0.00000 $0.00544
Haiku 4.5 $0.00000 $0.00272

Measured 11d ago against content hash a860f0b88db9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

sprint-progress-tracker 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 11d 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.

.claude/skills/sprint-progress-tracker/SKILL.md · 366 lines

How it starts

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



name: "sprint-progress-tracker" description: | Monitors and reports execution status across active sprints and tasks with real-time progress visibility. Activates when: checking sprint status, monitoring task progress, generating progress reports, calculating ETAs, identifying bottlenecks, or creating stakeholder status updates. Provides completion percentages, file counts, time elapsed, and estimated completion times. allowed-tools:

  • Read
  • Write
  • Grep
  • Glob
  • Bash
  • TodoWrite


Sprint Progress Tracker Skill

Role

You are the Sprint Progress Tracker, responsible for monitoring and reporting on execution status across active sprints and tasks.

Core Responsibilities

1. Status Monitoring

Objective: Determine current state of all sprints and tasks

Status Determination Methods:

A. TodoWrite List Analysis

  1. Read current todo list (TodoWrite maintains active task list)
  2. Extract task states: pending, in_progress, completed
  3. Count tasks by state
  4. Calculate completion percentage

B. File System Analysis

  1. Use Glob to check if sprint directories exist: glob "temp/sprint-*"
  2. Use Glob to count research files per task: glob "temp/sprint-XX/[task-id]-*/*.md"
  3. Use Glob to check for synthesis files: glob "temp/sprint-XX/*/synthesis.md"
  4. Use Glob to check for final reports: glob "reports/sprint-*-report.md"

C. Timestamp Analysis

  1. Use Bash to check file creation times: ls -lt temp/sprint-XX/
  2. Calculate time elapsed since sprint start (earliest file timestamp)
  3. Calculate time since last activity (most recent file timestamp)

Status States:

  • Not Started: Sprint directory doesn't exist
  • In Progress: Directory exists, files being created, no final report
  • Completed: Final report exists in reports/ directory
  • Stalled: No new files in >30 minutes (configurable threshold)
  • Failed: Error log exists or explicitly marked as failed

2. Progress Reporting

Objective: Generate human-readable status summaries

Read the full file on GitHub · 366 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. 11d ago First seen · 366 lines · 0 tokens per session scan A a860f0b88db9

Subscribe to this mod's changes

sprint-progress-tracker is a skill published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,722 tokens. 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.