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/apexiq/skillsmith/plannernpx skills add ApexIQ/skillsmith --skill plannergit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/planner)<a href="https://agentmods.dev/skills/apexiq/skillsmith/planner"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/planner.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.00031 | $0.01344 |
| Opus 5 | $0.00015 | $0.00672 |
| Sonnet 5 | $0.00006 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
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 6d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Planner — Feature Implementation Planning
Philosophy: The best code is the code you plan before you write. Every feature needs a clear plan with measurable acceptance criteria before the first line is written.
1. When to Use This Skill
- Starting a new feature or user story
- Breaking down a large task into subtasks
- Creating sprint/iteration plans
- Writing technical design documents
- Estimating effort and identifying risks
2. The Planning Framework
Step 1: Problem Definition
Before planning solutions, nail the problem:
| Question | Example Answer |
|---|---|
| What problem does this solve? | Users can't reset passwords without support |
| Who is affected? | All 12K active users |
| What does success look like? | Self-service password reset in < 2 minutes |
| What are the constraints? | Must work with existing OAuth provider |
| What's the deadline? | Sprint 14 (2 weeks) |
Step 2: Requirements Decomposition
Break the feature into atomic units:
## Feature: Self-Service Password Reset
### Functional Requirements
1. FR-1: User can request a password reset via email
- Acceptance: Email sent within 30s of request
- Edge case: Invalid email returns generic "if account exists" message
2. FR-2: Reset link expires after 1 hour
- Acceptance: Expired links show clear error with re-request option
- Edge case: Multiple requests invalidate previous links
3. FR-3: New password must meet security policy
- Acceptance: Real-time validation feedback on password strength
- Edge case: Password same as last 5 passwords is rejected
### Non-Functional Requirements
- NFR-1: Reset flow completes in < 2 minutes end-to-end
- NFR-2: Rate-limited to 5 requests per email per hour
- NFR-3: All reset events logged for security audit
Step 3: Task Sequencing
Order tasks by dependency, not importance:
## Implementation Plan
### Phase 1: Backend Foundation (Day 1-2)
- [ ] T1: Create password_reset table migration
- [ ] T2: Implement token generation service
- [ ] T3: Implement email sending service
- [ ] T4: Create POST /api/auth/reset-request endpoint
- [ ] T5: Create POST /api/auth/reset-confirm endpoint
### Phase 2: Frontend (Day 3-4)
- [ ] T6: Create ResetRequestForm component
- [ ] T7: Create ResetConfirmForm component
- [ ] T8: Add password strength indicator
- [ ] T9: Wire up API calls and error handling
### Phase 3: Testing & Polish (Day 5)
- [ ] T10: Write unit tests for token service
- [ ] T11: Write integration tests for reset flow
- [ ] T12: Write E2E test for happy path
- [ ] T13: Security review of token handling
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.
- 6d ago First seen · 159 lines · 31 tokens per session scan A 9b48a90887b8
planner is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 1,344 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-31.
Other skills, from other repositories
release
Autonomously cut a Rove (@sma1lboy/rove) release end-to-end — detect the semver bump from pending changesets (flagging an upstream minor you didn't intend), run the release gates, bump/tag/push via scripts/release.sh, then poll the GitHub Actions Release workflow with gh until npm publish completes, diagnosing CI…
hyperframes-cli
HyperFrames CLI dev loop. Use when running npx hyperframes init, add, catalog, capture, lint, validate, inspect, layout, snapshot, preview, play, render, publish, lambda, doctor, browser, info, upgrade, skills, compositions, docs, benchmark, telemetry, transcribe, or remove-background, or when troubleshooting the…
changelog-generator
Draft Rove release notes as Changesets. Writes user-facing entries as .changeset/.md files for @sma1lboy/rove (consumed into packages/kobe/CHANGELOG.md at release time). Use when the user asks for "changelog", "release notes", "what changed", "add a changeset", or before cutting a version. Enforces Rove's no-soft-wrap…
pstack
Rigorous engineering mode for nontrivial work in this repo — a set of named principles plus the leaf skills that apply them. Use when the user says "pstack", "go deep", "be rigorous", "认真做", or when a task involves architecture, a real bug, a refactor, or anything the user will not be watching. Ported from…
pptx
Extract text from Microsoft PowerPoint presentations.
xlsx
Extract data from Excel and CSV files.