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 agentmods add skills/hoavdc/codexkit/codexkit-sprint-planning-assistantnpx skills add hoavdc/CodexKit --skill codexkit-sprint-planning-assistantgit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-sprint-planning-assistant)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-sprint-planning-assistant"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-sprint-planning-assistant.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 | $0.00061 | $0.00750 |
| Opus 5 | $0.00030 | $0.00375 |
| Sonnet 5 | $0.00012 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
codexkit-sprint-planning-assistant 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sprint Planning Assistant
Purpose
Turn a groomed backlog into a well-scoped sprint plan with clear commitments, dependencies, and capacity fit.
When to use
- preparing for a sprint planning meeting
- organizing and estimating a batch of backlog items
- checking if proposed sprint scope fits team capacity
- documenting sprint goals and commitments for stakeholders
When not to use
- strategic product planning or roadmapping
- items are not groomed (requirements unclear, no acceptance criteria)
- portfolio-level work intake or project governance
Inputs
- backlog items (titles, descriptions, acceptance criteria)
- team capacity (available person-days, holidays, known absences)
- sprint duration (typically 1 or 2 weeks)
- velocity reference (last 3 sprints if available)
- known dependencies or blockers
- sprint goal or theme from product owner
Procedure
- Review backlog items and confirm each has clear acceptance criteria.
- Flag items that are too large for one sprint and recommend splitting.
- Estimate effort using story points or T-shirt sizing.
- Map total estimated effort against team capacity and historical velocity.
- Identify cross-team or technical dependencies.
- Recommend a sprint commitment — items that fit capacity with 20% buffer.
- Write the sprint goal as one sentence.
- Produce a sprint summary table for stakeholders.
Output
- sprint goal statement
- committed items table (item, estimate, owner, dependency)
- stretch items (if capacity allows)
- flagged risks or blockers
- capacity utilization summary
Definition of done
- total committed effort is ≤ 80% of team capacity
- every committed item has an owner
- dependencies are explicitly called out
- sprint goal is one clear sentence tied to business value
Examples
- "Plan Sprint 12 with these 15 backlog items for a 5-person team over 2 weeks."
- "Check if we can fit the payment feature plus 3 bug fixes into next sprint."
- "Write a sprint summary for stakeholders — what we're committing to and why."
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 93 lines · 61 tokens per session scan A 1d443a84bc45
codexkit-sprint-planning-assistant is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 750 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
cultivating-personas
Distills AI agent voice patterns from conversation into a Persona Voice Card v1.0 (self/user/language/register/emojipolicy/flourish only — no judgment-shaped fields), validates schema + content safety + differentiation, and routes contributions through the existing submission portal. Use when the user wants to…
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.