Borrowing it
Nothing to install: this file belongs to josecoelho/obsidian-tasks-caldav. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/josecoelho/obsidian-tasks-caldav/master/.claude/commands/pm/plan.mdgit clone --depth 1 https://github.com/josecoelho/obsidian-tasks-caldavWrote 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/commands/josecoelho/obsidian-tasks-caldav/plan)<a href="https://agentmods.dev/commands/josecoelho/obsidian-tasks-caldav/plan"><img src="https://agentmods.dev/badge/commands/josecoelho/obsidian-tasks-caldav/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/commands/josecoelho/obsidian-tasks-caldav/plan"><img src="https://agentmods.dev/badge/commands/josecoelho/obsidian-tasks-caldav/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.00000 | $0.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
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.
What it actually says
Break down a feature into multiple GitHub issues using sub-issues for hierarchy.
Input: $ARGUMENTS
Steps:
- Parse the feature description in $ARGUMENTS
- If the description is too vague to decompose, ask clarifying questions first
- Analyze the feature and break it into discrete work items. For each item, determine:
- What code needs to change (consult the codebase)
- Which area it touches (caldav, sync, obsidian-ui, tasks-plugin, infra)
- Whether it depends on other items in the plan
- What testing approach it needs (E2E / unit / manual per CLAUDE.md)
- Present the plan as a numbered list showing:
- Title for each issue
- Labels (priority, area, type)
- Dependencies (which items must complete first)
- Brief acceptance criteria
- Ask the user to confirm or adjust the plan
- Once confirmed, create a parent tracking issue for the feature, then create each work item as a sub-issue:
a. Create the parent issue:
b. Create each child issue withgh issue create --title "Feature: <name>" --body "..." --label "feature,<area>,<priority>"gh issue create(with labels, acceptance criteria, testing notes, and "Blocked by #N" for dependencies) c. Link children as sub-issues of the parent:
Get node IDs via:gh api graphql -f query='mutation { addSubIssue(input: {issueId: "<parent_node_id>", subIssueId: "<child_node_id>"}) { issue { id } } }'gh issue view <number> --json id -q .id - Output the parent issue URL and all sub-issue URLs
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 · 31 lines · 0 tokens per session scan A d06d69afa9ac
plan is a command published in the GitHub repository josecoelho/obsidian-tasks-caldav (42 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Synchronizes your local swarm state with the latest GitHub repository state, updating task statuses and detecting changes.
claim
Claims a GitHub issue for your swarm to work on, preventing conflicts with other swarms.
weekly-summary
Generate weekly work summary from git activity.
next
Suggest the most likely next workflow action based on current context.
update-check.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.