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 Xiaowen-Jiang/agent-enterprise --skill project_planninggit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/xiaowen-jiang/agent-enterprise/project_planning)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/project_planning"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/project_planning.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.00014 | $0.00329 |
| Opus 5 | $0.00007 | $0.00164 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
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 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.
What it actually says
Process
- Understand the goal: What is the desired outcome? Who is it for?
- Identify major phases: Break into 3-5 phases (e.g., Design, Build, Test, Deploy)
- Break into tasks: Each phase gets specific, actionable tasks
- Identify dependencies: Which tasks block others?
- Assign ownership: Who on the team should handle each task?
- Estimate scope: Classify each task as Small/Medium/Large
Output Format
Project: [Name]
Goal: [One sentence]
Phase 1: [Name]
| Task | Owner | Size | Depends On |
|---|---|---|---|
| ... | ... | S/M/L | ... |
Phase 2: [Name]
...
Risks & Mitigations
- Risk: [what could go wrong] → Mitigation: [how to prevent/handle]
Success Criteria
- Measurable outcome 1
- Measurable outcome 2
Guidelines
- Tasks should be concrete and verifiable ("Create API endpoint" not "Do backend work")
- Each task should be completable by one person
- Flag tasks that need skills the team doesn't have
- Consider budget constraints (token costs for AI agents)
- Include a testing/validation phase
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 · 45 lines · 14 tokens per session scan A 5bdbfeec03d4
Project Planning is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 329 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 skills, from other repositories
workspace-manager
Registers, lists, removes, and assigns workspaces (project directories) for Anima work. Use when: binding project paths to Anima, managing aliases, or switching workspace roots.
giving-feedback
Structures effective feedback conversations using the Situation-Behaviour-Impact (SBI) model from the Center for Creative Leadership. Separates observable behavior from interpretation, anchors feedback in specific situations, and articulates concrete impact. Use when preparing difficult performance conversations…
hackman-enabling-conditions
Diagnoses and designs team effectiveness using Hackman's six enabling conditions: a real team, compelling direction, right people, sound structure, supportive context, and expert coaching. Shifts focus from blaming team members to establishing the structural and environmental conditions that make high performance…
leadership-pipeline
Diagnoses leadership development blockages using Charan's six passage transitions from individual contributor through enterprise manager. Evaluates skills, time allocation, and values shifts required at each leadership level. Use when founders cannot let go of operational tasks, managers are failing after promotion…
leadership-style-adaptation
Provides practical self-diagnosis exercises and daily habits for recognising when a leader's default style fails and adapting in real time. Focuses on behavioural flexibility rather than theory -- how to read the room, when to shift approach, and how to stay authentic while flexing. Complements the theoretical models…
situational-leadership
Matches leadership style to follower development level using Hersey and Blanchard's Situational Leadership model. Maps four styles -- directing, coaching, supporting, delegating -- to four development levels based on competence and commitment per task. Use when diagnosing style mismatches causing disengagement…