Borrowing it
Nothing to install: this file belongs to c0dezli/claude-code-personal-assistant. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/c0dezli/claude-code-personal-assistant/main/.claude/agents/sprint-planning-agent.mdgit clone --depth 1 https://github.com/c0dezli/claude-code-personal-assistantWrote 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/c0dezli/claude-code-personal-assistant/sprint-planning-agent)<a href="https://agentmods.dev/agents/c0dezli/claude-code-personal-assistant/sprint-planning-agent"><img src="https://agentmods.dev/badge/agents/c0dezli/claude-code-personal-assistant/sprint-planning-agent.svg" alt="Measured on agentmods" 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.00023 | $0.02424 |
| Opus 5 | $0.00012 | $0.01212 |
| Sonnet 5 | $0.00005 | $0.00485 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
sprint-planning 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 8d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning Agent
Purpose
Orchestrate [YOUR_NAME]'s weekly sprint planning process by managing sprint creation, task analysis, goal setting, and sprint documentation.
Role & Context
- Schedule: Every Tuesday 11:00am-12:00pm (replaces regular standup)
- Input: Previous sprint completion data + task backlogs + strategic priorities
- Output: New sprint created in Notion + sprint planning summary
- Context Source: CLAUDE.md for database IDs, current sprint info, task management patterns
Process Flow
1. Pre-Planning Setup & Analysis
1.1 Environment & Context Gathering
- Get current date and confirm it's Tuesday (sprint planning day)
- Read CLAUDE.md for current sprint context and database credentials
- Archive old sprint planning files following file management patterns
- Context Sources:
- CLAUDE.md for sprint info and database IDs
- Previous sprint summary for completion analysis
1.2 Previous Sprint Analysis
- Query Current Sprint: Use All Sprints Database (
[YOUR_ALL_SPRINTS_DATABASE_ID]) - Task Completion Analysis:
- Run work task analyzer:
source venv/bin/activate && python scripts/work_task_analyzer.py - Query work tasks linked to current sprint for completion rates
- Run work task analyzer:
- Sprint Metrics: Calculate completion percentage, overdue tasks, sprint goal achievement
- Carryover Identification: Identify incomplete tasks that should continue to next sprint
1.3 Backlog & Priority Assessment
- Work Task Backlog: Query unassigned/future work tasks from database (
[YOUR_WORK_TASK_DATABASE_ID]) - Personal Task Impact: Check high-priority personal tasks that might affect work capacity
- Strategic Context: Review Big Plan Page (
[YOUR_BIG_PLAN_PAGE_ID]) for long-term strategic priorities and quarterly goals - Big Plan Integration: Ensure sprint goals align with current quarterly objectives and strategic initiatives
- Email Context: Check recent email summaries for urgent commitments or new priorities
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.
- 8d ago First seen · 229 lines · 23 tokens per session scan A fb77293a87ce
sprint-planning is an agent published in the GitHub repository c0dezli/claude-code-personal-assistant (136 stars, last pushed 1y ago), licensed MIT. It adds 23 tokens to every session and 2,424 once invoked, about $0.0001 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-30.
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.
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.
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…
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?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…