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 DauQuangThanh/hanoi-rainbow --skill project-planninggit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/project-planning)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/project-planning"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/project-planning/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/dauquangthanh/hanoi-rainbow/project-planning"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/project-planning.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.00106 | $0.01139 |
| Opus 5 | $0.00053 | $0.00570 |
| Sonnet 5 | $0.00021 | $0.00228 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
project-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 10d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planning
Overview
This skill provides comprehensive guidance for planning and managing software projects using industry best practices. It covers breaking down requirements into manageable tasks, estimating effort, organizing sprints, managing backlogs, and tracking progress effectively.
Key Principles:
- Adapt practices to team size and project complexity
- Start simple, add complexity as needed
- Focus on delivering value, not following process
- Regular inspection and adaptation are key
- Maintain sustainable pace, avoid burnout
Planning Workflow
Follow this workflow when planning software projects:
1. Define Project Scope
- Vision Statement: Clear project purpose and objectives
- Success Criteria: Measurable outcomes that define success
- Stakeholders: Identify all stakeholders and their roles
- Constraints: Budget, timeline, resources, technical limitations
- Deliverables: Core features, documentation, training materials
2. Break Down Requirements
- Transform requirements into epics (large bodies of work)
- Break epics into user stories: "As a [role], I want [feature] so that [benefit]"
- Create technical tasks from user stories
- Define acceptance criteria for each story
3. Estimate Effort
- Use story points (Fibonacci: 1, 2, 3, 5, 8, 13) for relative sizing
- Conduct planning poker for team consensus
- Apply three-point estimation for critical/uncertain tasks
4. Organize and Prioritize
- Group work into sprints (1-4 weeks)
- Prioritize using MoSCoW (Must/Should/Could/Won't) or Value vs. Effort
- Manage backlog with clear prioritization tiers: Now, Next, Later, Backlog
5. Track and Adjust
- Monitor sprint progress and velocity
- Identify and manage risks (technical, schedule, resource, external)
- Conduct regular retrospectives and adapt practices
User Story Format
**Title**: [Action] as [Role]
**As a** [user type]
**I want** [goal/feature]
**So that** [business value/benefit]
**Acceptance Criteria:**
- [ ] [Testable criterion 1]
- [ ] [Testable criterion 2]
- [ ] [Testable criterion 3]
**Priority**: [High/Medium/Low]
**Estimated Effort**: [X story points]
**Dependencies**: [List any dependencies]
What ships with it
12 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.
- references/anti-patterns-to-avoid.md 660 B
- references/backlog-not-prioritized.md 3.1 KB
- references/core-planning-workflow.md 5.5 KB
- references/external-dependencies.md 2.9 KB
- references/integration-with-development-workflow.md 758 B
- references/later-future.md 177 B
- references/next-2-3-sprints.md 187 B
- references/now-sprint-ready.md 186 B
- references/schedule-risks.md 226 B
- references/task-management-best-practices.md 2.8 KB
- references/technical-risks.md 407 B
- references/templates-and-checklists.md 1.2 KB
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.
- 10d ago First seen · 110 lines · 106 tokens per session scan A 4f0d24947ec2
project-planning is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 106 tokens to every session and 1,139 once invoked, about $0.0005 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
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.