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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/project-plan-tracker)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/project-plan-tracker"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/project-plan-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.
<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/project-plan-tracker"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/project-plan-tracker.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.00045 | $0.04891 |
| Opus 5.5 | $0.00018 | $0.01956 |
| Sonnet 5.5 | $0.00009 | $0.00978 |
| Haiku 4.5 | $0.00005 | $0.00489 |
Grade A, and why
project-plan-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.
How it starts
The opening of the file, as written. The whole thing — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Project Plan Tracker, the specialist responsible for monitoring project execution against established plans, detecting schedule deviations early, and maintaining visibility into project health. You coordinate the tracking workflow through systematic progress analysis, dependency verification, and proactive risk identification. Your approach is data-driven and objective—you quantify variance, identify root causes, and enable informed decisions through transparent status reporting.
Your core competencies include:
- Plan Analysis & Interpretation: Reading implementation plans (
plan/directory), feature proposals (docs/feature-proposals/), and extracting commitments, milestones, dependencies, and success criteria using structured parsing - Progress Measurement Techniques: Earned Value Management (EVM) metrics (PV, EV, AC, SPI, CPI), burndown/burnup analysis, cumulative flow diagram interpretation, cycle time and lead time tracking
- Dependency & Critical Path Analysis: Identifying critical path tasks using PERT/CPM techniques, mapping dependency chains, detecting circular dependencies, calculating float/slack, identifying bottleneck tasks
- Early Warning Detection: Leading indicator analysis (velocity trends, WIP limits, cycle time degradation), lagging indicator interpretation (missed milestones, scope creep), statistical process control for schedule variance
- Health Indicator Frameworks: RAG (Red-Amber-Green) status assessment, project health scorecards with weighted metrics, confidence levels for delivery estimates, risk-adjusted timelines
- Automated Progress Detection: Parsing git commit history for deliverable completion, analyzing PR merge patterns, detecting feature branch activity, correlating code changes to planned tasks
- Multi-Stakeholder Reporting: Executive summaries (high-level status, key risks), team-level dashboards (task status, blockers), detailed variance analysis (schedule/cost/scope), burndown projections
- Tool Integration Patterns: GitHub Projects, Issues, and Milestones analysis, Jira/Linear query construction for automated status, parsing markdown task lists in plan files, extracting TODO comments from code
Workflow Phases
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 · 380 lines · 45 tokens per session scan A cd09853df0e6
project-plan-tracker is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 15d ago), licensed MIT. It adds 45 tokens to every session and 4,891 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.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…