Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/AcKeskin/contexturenpx agentmods add skills/ackeskin/contexture/draft-planWrote 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/ackeskin/contexture/draft-plan)<a href="https://agentmods.dev/skills/ackeskin/contexture/draft-plan"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/draft-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/ackeskin/contexture/draft-plan"><img src="https://agentmods.dev/badge/skills/ackeskin/contexture/draft-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.00085 | $0.04646 |
| Opus 5.5 | $0.00034 | $0.01858 |
| Sonnet 5.5 | $0.00017 | $0.00929 |
| Haiku 4.5 | $0.00009 | $0.00465 |
Grade A, and why
draft-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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
draft-plan
Run the plan flow — turn an active spec (or a degraded --task description) into a versioned, stepped implementation plan. Upstream of /execute; downstream of /spec. Plans pin to the exact spec version they were drafted against.
When to run
- User types
/draft-plan,/draft-plan <slug>, or/draft-plan <slug> --task "<text>". - User asks to "plan out", "break into steps", "draft an implementation plan" for a specced feature.
- After
/speclands, before/execute.
Do not auto-fire. For a one-sentence change, the triviality check (step 7) will short-circuit and tell the user to just do it.
Forms
/draft-plan(no slug) — resolve in this order: (1) ifdefaultis active in.claude/specs/INDEX.md, use it; (2) else if exactly one named slug is active, use it; (3) else list active slugs and ask./draft-plan <slug>— read.claude/specs/<slug>/active version, write.claude/plans/<slug>/v<N>.md./draft-plan <slug> --task "<text>"— degraded mode: no spec required, the text is the input. Slug still required for the output path. Usedefaultfor the no-decision case.--quiet— terse review gate: one accept/edit/reject prompt instead of an inline or outline walkthrough (step 9). Combinable with any form above.--executor cheap— strict drafting mode. Draft the plan for an executor that does not share this conversation and reasons less capably: every step self-contained, every judgment call closed at draft time (step 8b). Default is--executor main(this context executes; today's behaviour). Combinable with any form above.
Procedure
-
Locate the trees.
$CLAUDE_PROJECT_DIR/.claude/specs/and.claude/plans/(cwd fallback if env var unset). Lazy mkdir. -
Resolve the slug.
- Slug given → use it.
- No slug,
defaultis active in.claude/specs/INDEX.md→ usedefault. - No slug, no
defaultbut exactly one other active spec → use it. - No slug, multiple active → list active slugs and ask which.
- No slug, no specs → only valid with
--task(which itself requires an explicit slug); otherwise stop with: "No specs and no task description. Run/specfirst or pass<slug> --task." - Stale INDEX — INDEX.md names an active version whose file is missing on disk → stop with: "INDEX.md points at
<path>but the file is missing. Reconcile by re-running/spec <slug>, or pass an explicit path."
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 · 232 lines · 85 tokens per session scan A 1bcec224c0ee
draft-plan is a skill published in the GitHub repository AcKeskin/contexture (2 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 4,646 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
customer-success
Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.
event-planner
Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.
hr-talent
HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
operations
Operations excellence expertise for supply chain optimization, process improvement (Lean, Six Sigma), capacity planning, vendor management, quality assurance, and operational efficiency. Use when optimizing processes, managing supply chains, or improving operational performance.
process-flowchart-designer
Create process flowcharts and workflow diagrams from descriptions, with optimization suggestions and bottleneck identification. Use when mapping processes, designing workflows, or improving operational efficiency.