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/avksp/agent-lifecycle-kit/agent-first-planningnpx skills add avksp/agent-lifecycle-kit --skill agent-first-planninggit clone --depth 1 https://github.com/avksp/agent-lifecycle-kitWrote 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/avksp/agent-lifecycle-kit/agent-first-planning)<a href="https://agentmods.dev/skills/avksp/agent-lifecycle-kit/agent-first-planning"><img src="https://agentmods.dev/badge/skills/avksp/agent-lifecycle-kit/agent-first-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 | $0.00033 | $0.00682 |
| Opus 5 | $0.00016 | $0.00341 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
agent-first-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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent first planning
Use this skill when a request must become an agent-ready implementation plan before work starts. The output is a frozen-ready package, not implementation.
Contract
- Clarify only questions that can change scope, architecture, safety, acceptance, external authority, or write ownership. Record safe assumptions for everything else.
- Choose the SDD tier.
S0: one bounded mechanical change with one executable owner.S1: one standard owner and no major architecture, security, performance, browser, data, or external-environment risk.S2: multiple executable owners or meaningful architecture, security, performance, browser, data, release, migration, or external risk. Use the coretier resolvecommand when available, and never lower a tier without independent review.
- For
S2, write a product specification first and require independent specification review before plan freeze. - Produce a developer overview that explains the intent, user-visible result, architecture boundaries, risks, non-goals, and execution model.
- Produce a plan manifest or equivalent machine-readable contract with: requirements, acceptance criteria, evidence ids, workstreams, dependency DAG, exact write ownership, read-only inputs, lead-owned integration seams, validation commands, budgets, context limits, and final audit gates.
- Keep immutable planning authority separate from mutable run artifacts.
- Route the candidate plan to
audit-agent-plan. Revise until it isREADY_TO_FREEZE, explicitly blocked, or the review budget is exhausted.
When the CLI is available, run the structural gate before independent review:
agent-lifecycle plan completeness-check --manifest <plan.manifest.json>
agent-lifecycle plan check --manifest <plan.manifest.json> --require-completeness
The goal is compact-but-complete authority for the selected tier, not long prose. S0/S1 plans can stay short, but the fields required by their tier must be present.
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.
- 5d ago First seen · 74 lines · 33 tokens per session scan A e8dc5e8e01c2
agent-first-planning is a skill published in the GitHub repository avksp/agent-lifecycle-kit (18 stars, last pushed 3d ago), licensed Apache-2.0. It adds 33 tokens to every session and 682 once invoked, about $0.0002 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
analytics-tracking-v2
Analytics Tracking & Measurement Strategy workflow skill. Use this skill when the user needs Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
security-audit
Detects high-confidence security risks in code.
deep-clean
Full-spectrum consolidation of AI agent configuration files. Goes beyond memory-only dream skills: audits and optimizes context files (AGENTS.md/AGENTS.md/GEMINI.md/.cursorrules), rules, skills, and memory. Detects stale references, dead file paths, duplicated rules, stack mismatches, contradictions, vague directives…
changes-report
Report all repository changes that entered a target branch during one required date or period, grouped by product change and written as plain English for a broad audience. Use for daily, weekly, date-range, or relative-period change summaries rather than explaining one known diff.
jira-issue-create
Create one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.
claude-review
Run an independent Claude Opus review of the complete current change against the repository's default branch, then verify its findings locally. Use after focused checks pass when you want a second model to review the change before further edits or delivery.