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/syncgit 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.00012 | $0.00582 |
| Opus 5 | $0.00006 | $0.00291 |
| Sonnet 5 | $0.00002 | $0.00116 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
sync 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 2d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-User Sync
Synchronize decision graph with your team using event-based sync.
Step 1: Pull Latest
git pull --rebase
Step 2: Check Sync Status
deciduous events status
Look for:
- Pending events: Events from teammates not yet in your local DB
- Event files: Each teammate has their own
.jsonlfile
Step 3: Rebuild if Needed
If there are pending events:
# Preview what would change
deciduous events rebuild --dry-run
# Apply teammate events to your local database
deciduous events rebuild
Step 4: Push Your Changes
# Stage sync files (events are auto-committed to your event file)
git add .deciduous/sync/
# Commit and push
git commit -m "sync: decision graph events"
git push
Checkpoint (Periodic Maintenance)
To prevent repo bloat, periodically create a checkpoint:
# Create checkpoint and clear old events
deciduous events checkpoint --clear-events
# Commit the checkpoint
git add .deciduous/sync/
git commit -m "checkpoint: compact decision graph events"
git push
When to checkpoint:
- After major milestones
- When event files get large (>100KB)
- Before releases
Troubleshooting
Events not syncing?
- Make sure
.deciduous/sync/is tracked in git - Check that
deciduous events initwas run - Verify events are being emitted:
deciduous events status
Merge conflicts in event files?
Event files are append-only JSONL. Git should auto-merge them. If conflicts occur, accept both versions (both sets of events are valid).
Missing nodes after rebuild?
Nodes reference each other by change_id (UUID), not local id.
If edges fail, the referenced node may be in a teammate's events
that haven't been pulled yet. Pull and rebuild again.
Quick Reference
| Command | What it does |
|---|---|
deciduous events status |
Show pending events, authors, file sizes |
deciduous events rebuild |
Apply all events to local DB |
deciduous events rebuild --dry-run |
Preview without applying |
deciduous events checkpoint |
Snapshot current state |
deciduous events checkpoint --clear-events |
Snapshot + delete old events |
deciduous events emit <id> |
Manually emit event for a node |
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.
- 2d ago First seen · 97 lines · 12 tokens per session scan A e110c016f8f3
sync is a command published in the GitHub repository notactuallytreyanastasio/deciduous (160 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 582 once invoked, about $0.0001 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.