A planning guide that turns a feature’s defined checks into ordered implementation steps, with test descriptions and optional user-flow or security steps.

Use it to plan features, describe failing tests, map steps to checks, and add user-interface or security considerations when relevant.

It fills in the work between deciding what a feature must do and having a plan an agent can follow. Test-first descriptions make the expected behavior clear before implementation.

How jahala/umbel configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to jahala/umbel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jahala/umbel/master/.claude/skills/tend-plan/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/jahala/umbel

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jahala/umbel/tend-plan/github.svg)](https://agentmods.dev/skills/jahala/umbel/tend-plan)

Your own site

<a href="https://agentmods.dev/skills/jahala/umbel/tend-plan"><img src="https://agentmods.dev/badge/skills/jahala/umbel/tend-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jahala/umbel/tend-plan"><img src="https://agentmods.dev/badge/skills/jahala/umbel/tend-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,268 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00056	$0.04268
Opus 5	$0.00028	$0.02134
Sonnet 5	$0.00011	$0.00854
Haiku 4.5	$0.00006	$0.00427

Measured 9d ago against content hash 9749ac0317f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

tend-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 9d 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.

.claude/skills/tend-plan/SKILL.md · 333 lines

How it starts

The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Plan: Slots + Checks -> Implementation Steps (+ User Flow, Security, Test Specs)

Owns: steps[], entry_condition / exit_condition, and the test-spec content that lives inline in each step's description. May add security-related checks (via tend_update_feature merging into checks[]).

Purpose

Turn a feature with defined slots and checks into a complete, executable plan:

Implementation steps - typed, ordered steps forming a valid DAG. Each step traces to one or more checks[] IDs via traces_to. Each agent step with traces_to carries a Test: block leading its description (the failing-test-in-prose).
User-flow steps - if the feature has user-facing views, add tagged [action]/[assert]/[system] steps. See references/user-flow.md.
Security analysis - if the feature touches auth, payments, PII, or external integrations, add security checks. See references/security.md.
Test specifications - always; the Test block in every step. See references/test-design.md.

What this skill assumes

Skip planning for polyglots with data.persona or data.opportunity set. Catalog descriptions don't have steps to plan — their content lives in the structured fields (jobs / outcome_metric / etc.). Route to /tend position for authoring instead.
The feature exists with at least slots, checks, and a smoke decision (output of /tend brainstorm).
Each check the plan will trace to carries validates_job (or the feature has no bound personas with jobs). A missing validates_job means the failing-test prose has no human-grounded spec — back to /tend brainstorm before planning.
The catalog's bound persona-jobs are resolvable from catalog.personas[<id>].jobs[<idx>]. The validation text on each job is the spec the step's Test block must mirror.
The user has agreed in principle on the technical approach. This skill structures the work; it doesn't choose between competing approaches.

Phase 1: implementation plan

Read the full file on GitHub · 333 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

9d ago First seen · 333 lines · 56 tokens per session scan A 9749ac0317f4

Subscribe to this mod's changes

tend-plan is a skill published in the GitHub repository jahala/umbel (2 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 4,268 once invoked, about $0.0003 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.

Claude Code Planning agent-orchestration ai-tools automation bun mcp

factory-handoff

Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.

watt-mind/factory · 47 tokens

ticket-spec

Turn a raw Linear Triage ticket into a fully specified ai:agent-ready one by exploring the codebase. Use when specifying, refining, or promoting tickets, or when asked why a ticket isn't dispatchable.

watt-mind/factory · 45 tokens

swarm-pr-review

Run a graph-guided, tool-augmented PR review using context packing, parallel exploration, mandatory repository-agnostic risk-family coverage with dispatch scaled to diff size and risk, independent reviewer validation, critic challenge, and metrics writeback. Use for deep pull request review with low false-positive…

ZaxbyHub/opencode-swarm · 91 tokens

umbel: Skill for Claude Code