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 avibebuilder/claude-prime --skill give-plangit clone --depth 1 https://github.com/avibebuilder/claude-primeWrote 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/avibebuilder/claude-prime/give-plan)<a href="https://agentmods.dev/skills/avibebuilder/claude-prime/give-plan"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/give-plan/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/avibebuilder/claude-prime/give-plan"><img src="https://agentmods.dev/badge/skills/avibebuilder/claude-prime/give-plan.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.00111 | $0.00767 |
| Opus 5.5 | $0.00044 | $0.00307 |
| Sonnet 5.5 | $0.00022 | $0.00153 |
| Haiku 4.5 | $0.00011 | $0.00077 |
Grade A, and why
give-plan 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 1mo 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ultrathink
Core contract
Figure out the right approach, write a plan the user can inspect, and stop. Planning is not approval to implement — wait for explicit go-ahead before writing any code.
- Clarify only what would materially change the plan.
- Read the codebase before making claims. Distinguish confirmed facts, inferences, and unknowns — never hide uncertainty.
- Optimize for reviewability over momentum.
If already in native plan mode, this skill shapes how to plan; plan mode provides the workflow structure and must follow this skill guidelines.
Process
Check conversation context and skip completed steps.
1. Clarify the planning goal
What kind of plan? Scoped implementation, phased feature, migration/rollout, architecture decision, or spec artifact. Ask only the questions that matter.
2. Ground in evidence
Read relevant files and search the codebase before proposing changes. Be explicit about what's confirmed from code vs. inferred vs. unknown.
3. Choose the right altitude
- Small change → concise plan with touchpoints and validation
- Multi-file feature → phased plan with dependencies
- Architecture choice → options, tradeoffs, recommendation
- Migration / rollout → sequencing, rollback, validation checkpoints
Don't force every request into the same template.
4. Write the plan (right-size the artifact)
Match artifact to plan size — don't force plans/*.md on small scoped changes.
- Inline prose — small single-file tweaks, quick scoped edits, brief decisions. Present the plan in the response and stop.
plans/YYYYMMDDHHMMSS-{plan-name}.md— multi-file features, migrations, architecture decisions, anything that benefits from review or history.plans/YYYYMMDDHHMMSS-{plan-name}/plan.md+ phase files — large multi-phase work where each phase warrants independent reading/editing.
Use date +%Y%m%d%H%M%S for timestamps.
A strong plan covers: problem summary, recommended approach, phases/workstreams, affected files/modules/systems, dependencies and sequencing, validation strategy, risks and mitigations, assumptions and open questions, non-goals when useful.
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.
- 1mo ago First seen · 61 lines · 111 tokens per session scan A 2508f5e63ede
give-plan is a skill published in the GitHub repository avibebuilder/claude-prime (120 stars, last pushed 5mo ago), licensed MIT. It adds 111 tokens to every session and 767 once invoked, about $0.0004 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-30.
Other skills, from other repositories
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
contract-and-proposal-writer
Generate professional, jurisdiction-aware business documents: freelance contracts, project proposals, SOWs, NDAs, and MSAs. Structured Markdown output with docx conversion instructions. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) jurisdictions. Not a substitute for legal counsel — use as strong starting…
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and…
process-mapper
Use when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…