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 legacybridge-tech/claude-plugins --skill manage-sprintgit clone --depth 1 https://github.com/legacybridge-tech/claude-pluginsWrote 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/legacybridge-tech/claude-plugins/manage-sprint)<a href="https://agentmods.dev/skills/legacybridge-tech/claude-plugins/manage-sprint"><img src="https://agentmods.dev/badge/skills/legacybridge-tech/claude-plugins/manage-sprint.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.00077 | $0.05671 |
| Opus 5 | $0.00039 | $0.02835 |
| Sonnet 5 | $0.00015 | $0.01134 |
| Haiku 4.5 | $0.00008 | $0.00567 |
Grade A, and why
manage-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 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 — 920 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Sprint Skill
When to use this Skill
Activate when the user:
- Mentions creating, starting, or managing sprints/iterations
- Uses keywords: "sprint", "iteration", "user story", "backlog", "velocity", "scrum"
- Wants to track work items (stories, tasks, bugs)
- References sprint ceremonies (planning, review, retrospective)
- Needs to update sprint status or progress
- Talks about Kanban boards or workflow states
Workflow
This Skill handles multiple sprint-related operations. The workflow adapts based on user intent and project methodology.
Phase 1: Context Discovery & Intent Recognition
Objective: Understand project methodology and user's specific intent.
Steps:
-
Locate and read RULE.md:
ls RULE.md Read RULE.md -
Extract methodology configuration:
Key fields: - methodology: [scrum|kanban|waterfall|agile|hybrid] - sprint_length: [1_week|2_weeks|3_weeks|4_weeks] (if Scrum) - workflow_stages: [list] (if Kanban) - ceremonies: [list] (if Scrum) -
Understand directory structure:
- Scrum:
sprints/directory with numbered sprints - Kanban:
board/directory with workflow stages - Agile/Hybrid:
iterations/orwork/directory
- Scrum:
-
Detect user intent from message:
- Create new sprint/iteration: "start sprint", "create sprint", "new sprint"
- Update sprint status: "sprint progress", "update sprint", "completed story"
- Add work items: "add user story", "create task", "new card"
- Complete sprint: "finish sprint", "sprint review", "close sprint"
- View sprint status: "sprint status", "what's in this sprint", "show backlog"
- Move items: "move to in-progress", "done with task"
-
Route to appropriate sub-workflow:
- Intent: Create → Workflow A (Create Sprint)
- Intent: Update → Workflow B (Update Sprint)
- Intent: Add items → Workflow C (Add Work Items)
- Intent: Complete → Workflow D (Complete Sprint)
- Intent: Status → Workflow E (Report Status)
- Intent: Move → Workflow F (Update Item Status)
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 · 920 lines · 77 tokens per session scan A 570a1125c852
manage-sprint is a skill published in the GitHub repository legacybridge-tech/claude-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 5,671 once invoked, about $0.0004 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.