deciduous: Command for Claude Code

.claude/commands/work.md

work is a command for Claude Code from notactuallytreyanastasio/deciduous. It costs 11 tokens per session (1,025 once invoked), scanned A, original, Apache-2.0.

A work-start command that records the user's request as a goal before implementation begins.

In plain words
What is it for?
Use it before coding to create a goal, record action nodes for major edits, link those actions to the goal, and record the outcome when the work is finished.
Why use it?
It creates a traceable link between the requested work, the code changes, and the final result, and can prevent edits without recent project context.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is notactuallytreyanastasio/deciduous's own configuration. It tells Claude Code how to work on deciduous itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything deciduous configures →

Reuse

Borrowing it

Nothing to install: this file belongs to notactuallytreyanastasio/deciduous. 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/notactuallytreyanastasio/deciduous/main/.claude/commands/work.md
Clone the repo
git clone --depth 1 https://github.com/notactuallytreyanastasio/deciduous

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.

agentmods badge for work

README.md
[![agentmods](https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/work/github.svg)](https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/work)
Your own site
<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/work"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/work/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.

agentmods 80×15 button for work

Your own site · 80×15
<a href="https://agentmods.dev/commands/notactuallytreyanastasio/deciduous/work"><img src="https://agentmods.dev/badge/commands/notactuallytreyanastasio/deciduous/work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,025 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00011 $0.01025
Opus 5.5 $0.00004 $0.00410
Sonnet 5.5 $0.00002 $0.00205
Haiku 4.5 $0.00001 $0.00103

Measured 13d ago against content hash a3896b4f0874, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

work 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 13d 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/commands/work.md · 131 lines

How it starts

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

Work Transaction

USE THIS BEFORE STARTING ANY IMPLEMENTATION.

This skill creates the required deciduous nodes BEFORE you write any code. The Edit/Write hooks will BLOCK you if you don't have a recent node.

Step 1: Create the Goal Node

Based on $ARGUMENTS (or the user's most recent request), create a goal node:

# Create goal with the user's request captured verbatim
deciduous add goal "$ARGUMENTS" -c 90 --prompt-stdin << 'EOF'
[INSERT THE EXACT USER REQUEST HERE - VERBATIM, NOT SUMMARIZED]
EOF

IMPORTANT: The prompt must be the user's EXACT words, not your summary.

Step 2: Announce the Goal ID

After creating the goal, tell the user:

  • The goal ID that was created
  • What you're about to implement
  • That you'll create action nodes as you work

Step 3: Before Each Major Edit

Before editing files, create an action node:

deciduous add action "What you're about to implement" -c 85 -f "file1.rs,file2.rs"
deciduous link <goal_id> <action_id> -r "Implementation step"

Other agents working at the same time? Before editing a file another agent may be changing, read deciduous board read --unanswered <your-label>, and post an interface change on the board (deciduous board post --as <your-label> -s "..." -m "@owner ...") before you make it. Never coordinate through a scratch or markdown file.

Step 4: After Completion

When the work is done:

# After committing
deciduous add outcome "What was accomplished" -c 95 --commit HEAD
deciduous link <action_id> <outcome_id> -r "Implementation complete"

# Anything the graph server has not got?
deciduous remote status

Before you report the work finished, check the board once more (deciduous board read --unanswered <your-label>) and answer what is there with --reply-to <id>.

Step 5: Attach Supporting Documents (Optional)

If the work produced or referenced important files (diagrams, specs, screenshots):

deciduous doc attach <goal_id> path/to/diagram.png -d "Architecture diagram"
deciduous doc attach <action_id> path/to/spec.pdf --ai-describe

Read the full file on GitHub · 131 lines

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.

  1. 13d ago Changed a3896b4f0874
  2. 1mo ago Changed · +8 lines ab56ee9c3d04
  3. 2mo ago First seen · 123 lines · 11 tokens per session scan A 7ed85e69085c

Subscribe to this mod's changes

work is a command published in the GitHub repository notactuallytreyanastasio/deciduous (169 stars, last pushed 13d ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,025 once invoked, about $0.0000 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.

Related

work compared with commands from other repositories

work next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
worknotactuallytreyanastasio/deciduousCommand16913d agoApache-2.0A11Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code