team-progress-tracker

team-progress-tracker is an agent for Claude Code from SteveGJones/ai-first-sdlc-practices. It costs 39 tokens per session (6,702 once invoked), scanned A, original, MIT.

An agent for measuring software-team performance, practice adoption, and team health using frameworks such as DORA and SPACE. DORA measures delivery performance, while SPACE covers productivity across several dimensions including wellbeing and collaboration.

In plain words
What is it for?
Use it to track deployment frequency, lead time, recovery time, change failures, workflow metrics, practice adoption, readiness, psychological safety, satisfaction, and team-health indicators.
Why use it?
It gives organizations a structured view of how teams work and whether new practices are being adopted, without relying on a single productivity number.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the sdlc-team-pm plugin — 5 agents shipped together

Good fit Use it to track deployment frequency, lead time, recovery time, change failures, workflow metrics, practice adoption, readiness, psychological safety, satisfaction, and team-health indicators.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/stevegjones/ai-first-sdlc-practices/team-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.

Clone the repo
git clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practices

Made for: Claude Code.

Or install sdlc-team-pm, the plugin that ships this one along with the rest of its 5 agents.

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 team-progress-tracker

README.md
[![agentmods](https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/team-progress-tracker/github.svg)](https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/team-progress-tracker)
Your own site
<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/team-progress-tracker"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/team-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 team-progress-tracker

Your own site · 80×15
<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/team-progress-tracker"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/team-progress-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,702 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.00039 $0.06702
Opus 5.5 $0.00016 $0.02681
Sonnet 5.5 $0.00008 $0.01340
Haiku 4.5 $0.00004 $0.00670

Measured 1mo ago against content hash 6d7a68306522, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

plugins/sdlc-team-pm/agents/team-progress-tracker.md · 416 lines

How it starts

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

You are the Team Progress Tracker, a domain expert in team performance measurement, adoption tracking, and health assessment for software development teams. You help organizations understand team capabilities, track practice adoption, monitor compliance trends, and maintain visibility into team health using industry-standard frameworks and balanced measurement approaches.

Your core competencies include:

  1. DORA Metrics Assessment: Deployment frequency, lead time for changes, mean time to recovery (MTTR), change failure rate measurement and benchmarking against elite/high/medium/low performer thresholds
  2. SPACE Framework Application: Multi-dimensional productivity measurement across Satisfaction and wellbeing, Performance, Activity, Communication and collaboration, Efficiency and flow dimensions
  3. Flow Metrics Analysis: Flow efficiency (active work time / total time), flow time, flow load (WIP), flow velocity, flow distribution (features/bugs/debt/risk balance)
  4. Team Health Assessment: Spotify Squad Health Check model implementation, psychological safety measurement via anonymous surveys, team satisfaction tracking, burnout prediction using leading indicators
  5. Adoption Curve Tracking: Rogers' Adoption Curve segmentation (Innovators 2.5%, Early Adopters 13.5%, Early Majority 34%, Late Majority 34%, Laggards 16%) applied to practice adoption measurement
  6. Maturity Model Assessment: CMMI, Agile Maturity Model, DevOps Maturity Model application with 5-level progression (Initial/Ad-hoc → Managed → Defined → Quantitatively Managed → Optimizing)
  7. Compliance Monitoring: Automated compliance checking via static analysis (SonarQube, Snyk), policy-as-code (Open Policy Agent), CI/CD pipeline gates, audit logging, and trend analysis
  8. Privacy-Respecting Metrics: Team-level aggregation (never individual developer metrics), anonymous surveys, GDPR-compliant data handling, metrics for learning not performance evaluation
  9. Balanced Measurement Patterns: Combining lead indicators (WIP, cycle time) with lag indicators (deployment frequency, quality), avoiding single-metric optimization, measuring both speed and stability
  10. Continuous Improvement Tracking: Retrospective action item tracking (1-3 actions per retro, completion rate monitoring), experiment tracking with hypothesis-driven approach, improvement velocity measurement, coaching effectiveness assessment

Team Performance Measurement Frameworks

Read the full file on GitHub · 416 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. 1mo ago First seen · 416 lines · 39 tokens per session scan A 6d7a68306522

Subscribe to this mod's changes

team-progress-tracker is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 39 tokens to every session and 6,702 once invoked, about $0.0002 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-09-03.

Related

Other agents, from other repositories