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.
npx skills add jrjsmrtn/project-orchestration-skills --skill plan-sprintgit clone --depth 1 https://github.com/jrjsmrtn/project-orchestration-skillsWrote 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/skills/jrjsmrtn/project-orchestration-skills/plan-sprint)<a href="https://agentmods.dev/skills/jrjsmrtn/project-orchestration-skills/plan-sprint"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/plan-sprint/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/skills/jrjsmrtn/project-orchestration-skills/plan-sprint"><img src="https://agentmods.dev/badge/skills/jrjsmrtn/project-orchestration-skills/plan-sprint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00039 | $0.01680 |
| Opus 5 | $0.00019 | $0.00840 |
| Sonnet 5 | $0.00008 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
plan-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 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Sprint
Create a sprint plan for a new development cycle.
When to Use
- Starting a new sprint
- After completing
wrapup-sprintfor previous sprint - When initializing Sprint 1 for a new project
Required Inputs
- Sprint number (e.g., 1, 2, 3)
- Sprint goal (1-2 sentence objective)
- Deliverables or user stories with acceptance criteria
Workflow
Step 1: Determine Sprint Context
Check current project state:
# Get current date
date +%Y-%m-%d
# Check latest version
git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet"
# Check previous sprint (if any)
ls docs/sprints/sprint-*-plan.md 2>/dev/null | tail -1
# Check current roadmap phase
cat docs/roadmap/roadmap.md 2>/dev/null | head -30
Calculate:
- Sprint number: Previous + 1, or 1 if first sprint
- Target version: Current patch + 1 (e.g., v0.1.2 → v0.1.3)
- Current phase: From roadmap (e.g., "Phase 1: Foundation")
- Start date: Today
Step 2: Choose Sprint Plan Format
Two formats are available. Choose based on project type:
- Minimal — for technical/infrastructure projects or highly focused sprints: deliverables with acceptance criteria, no user stories
- Structured — for user-facing projects or projects needing traceability: user stories with acceptance criteria
Step 3: Create Sprint Plan
Create docs/sprints/sprint-NNNN-plan.md (4-digit zero-padded, e.g., sprint-0001-plan.md):
Minimal Format
# Sprint [N] — [Goal Line]
**Target Version**: v0.1.x
**Phase**: [Current roadmap phase, e.g., "Phase 1: Foundation"]
**Status**: In Progress
**Started**: [Date]
## Goal
[1-2 sentence problem statement — what this sprint accomplishes and why]
## Context
[Only if this sprint builds on prior sprints or requires background. Otherwise omit.]
## Deliverables
### 1. [Component/Module Name]
- [Feature or change 1]
- [Feature or change 2]
### 2. [Another Component]
- [Feature or change 1]
## Files
| Action | File |
|--------|------|
| Create | `path/to/new/file` |
| Modify | `path/to/existing/file` |
## Acceptance Criteria
- [ ] [Specific, verifiable requirement 1]
- [ ] [Specific, verifiable requirement 2]
- [ ] All tests passing
- [ ] Code quality gates pass (format, lint, etc.)
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.
- 11d ago First seen · 255 lines · 39 tokens per session scan A 6f63c2a0112b
plan-sprint is a skill published in the GitHub repository jrjsmrtn/project-orchestration-skills (15 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 1,680 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-30.
Other skills, from other repositories
c-jira
Manage Jira issues using jira (jira-cli). List and filter issues, create new tickets, transition issue status, manage sprints, and add comments — all from the terminal without opening a browser.
linear
Linear project management — issues, cycles, and projects via GraphQL API.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.