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 agentmods add commands/notactuallytreyanastasio/deciduous/decisiongit clone --depth 1 https://github.com/notactuallytreyanastasio/deciduousWhat 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 | $0.00009 | $0.03483 |
| Opus 5 | $0.00005 | $0.01741 |
| Sonnet 5 | $0.00002 | $0.00697 |
| Haiku 4.5 | $0.00001 | $0.00348 |
Grade A, and why
decision 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 3d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision Graph Management
Log decisions IN REAL-TIME as you work, not retroactively.
When to Use This
| You're doing this... | Log this type | Command |
|---|---|---|
| Starting a new feature | goal with -p |
/decision add goal "Add user auth" -p "user request" |
| Choosing between approaches | decision |
/decision add decision "Choose auth method" |
| Considering an option | option |
/decision add option "JWT tokens" |
| About to write code | action |
/decision add action "Implementing JWT" |
| Noticing something | observation |
/decision add obs "Found existing auth code" |
| Finished something | outcome |
/decision add outcome "JWT working" |
| Reconsidering a past decision | revisit |
/decision add revisit "Reconsidering auth" |
What NOT to Log - CRITICAL
The decision graph records the USER'S project decisions, not your internal process.
Do NOT create nodes for your own thinking, planning, reading, or tooling steps. Only log things the user would recognize as project milestones or decisions.
Skip these (meta/process noise):
- "Reading codebase to understand structure"
- "Planning implementation approach"
- "Running tests to check status"
- "Analyzing existing code"
Log these (user-visible project work):
- "Add user authentication" (goal)
- "Use JWT tokens" (option)
- "Implemented JWT middleware" (action)
- "JWT auth working, all tests pass" (outcome)
Quick Commands
Based on $ARGUMENTS:
View Commands
nodesorlist->deciduous nodesedges->deciduous edgesgraph->deciduous graphcommands->deciduous commands
Create Nodes (with optional metadata)
add goal <title>->deciduous add goal "<title>" -c 90add decision <title>->deciduous add decision "<title>" -c 75add option <title>->deciduous add option "<title>" -c 70add action <title>->deciduous add action "<title>" -c 85add obs <title> -d <description>->deciduous add observation "<title>" -c 80 -d "<description>"- Observations MUST have both a title (short summary) and description (full detail)
add outcome <title>->deciduous add outcome "<title>" -c 90add revisit <title>->deciduous add revisit "<title>" -c 75
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.
- 3d ago First seen · 336 lines · 9 tokens per session scan A b83c3ba655fc
decision is a command published in the GitHub repository notactuallytreyanastasio/deciduous (160 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,483 once invoked, about $0.0000 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.