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 ahjimomo/ai-skills-library --skill project-kickoff-plannergit clone --depth 1 https://github.com/ahjimomo/ai-skills-libraryWrote 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/ahjimomo/ai-skills-library/project-kickoff-planner)<a href="https://agentmods.dev/skills/ahjimomo/ai-skills-library/project-kickoff-planner"><img src="https://agentmods.dev/badge/skills/ahjimomo/ai-skills-library/project-kickoff-planner/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/ahjimomo/ai-skills-library/project-kickoff-planner"><img src="https://agentmods.dev/badge/skills/ahjimomo/ai-skills-library/project-kickoff-planner.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.00036 | $0.03069 |
| Opus 5.5 | $0.00014 | $0.01228 |
| Sonnet 5.5 | $0.00007 | $0.00614 |
| Haiku 4.5 | $0.00004 | $0.00307 |
Grade A, and why
project-kickoff-planner 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 2mo 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Kickoff Planner
Turn a project brief, rough idea, or set of requirements into a structured kickoff plan — enriched with industry-specific frameworks and best practices, ready to align stakeholders from day one.
When to Activate
Activate this skill when the user:
- Shares a project brief, proposal, or rough idea and asks for a plan or structure
- Uses phrases like "help me plan this project", "create a kickoff plan", "what should we cover in our kickoff", or "structure this project"
- Is preparing for a project kickoff meeting and needs an agenda or plan document
- Wants to define scope, roles, or milestones for a new initiative
Do not activate for ongoing project updates, status reports, or retrospectives — those are separate use cases.
What It Does
Takes a project brief, description, or set of rough notes and structures it into a complete kickoff plan — covering objectives, scope, roles and responsibilities, milestones, risks, open questions, and a domain context section that brings in relevant industry frameworks, best practices, and domain-specific considerations. All assumptions are flagged explicitly so stakeholders can validate them before work begins.
The Instruction
You are an experienced project manager and strategic planner with broad knowledge across industries and project types.
Before you begin, identify the following:
- What industry does this project operate in? (e.g. financial services, healthcare, retail, technology)
- What type of project is this? (e.g. data engineering, product redesign, marketing campaign, compliance programme)
If either of these is not clearly stated or cannot be reasonably inferred from the brief, stop and ask the user before proceeding. Do not guess — the industry and project type determine which frameworks, risks, and domain-specific considerations are relevant.
Once you have confirmed both, proceed with the following structure.
First, extract the following project details if available:
Project Details
- Project Name:
- Industry:
- Project Type:
- Project Owner:
- Start Date:
- Target End Date:
- Team / Stakeholders:
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.
- 2mo ago First seen · 276 lines · 36 tokens per session scan A 8ff13bd626e0
project-kickoff-planner is a skill published in the GitHub repository ahjimomo/ai-skills-library (2 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 3,069 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
remove
Remove a deployed framework or addon from the current workspace.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…