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 instructions/notactuallytreyanastasio/deciduous/claude-mdgit clone --depth 1 https://github.com/notactuallytreyanastasio/deciduousWrote 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/instructions/notactuallytreyanastasio/deciduous/claude-md)<a href="https://agentmods.dev/instructions/notactuallytreyanastasio/deciduous/claude-md"><img src="https://agentmods.dev/badge/instructions/notactuallytreyanastasio/deciduous/claude-md.svg" alt="Measured on agentmods" 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 | $0.07367 | $0.07367 |
| Opus 5 | $0.03683 | $0.03683 |
| Sonnet 5 | $0.01473 | $0.01473 |
| Haiku 4.5 | $0.00737 | $0.00737 |
Grade A, and why
deciduous CLAUDE.md 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 today.
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.
This is a copy
95% identical to deciduous AGENTS.md — 47 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 884 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deciduous - Decision Graph Tooling
Decision graph tooling for AI-assisted development. Track every goal, decision, and outcome. Survive context loss. Query your reasoning.
The Two Modes
Every system has two stories:
| Mode | Question | Skill |
|---|---|---|
| Now | "How does this work?" | /pulse |
| History | "How did we get here?" | /narratives → /archaeology |
Now mode maps current design as decisions. History mode captures evolution and pivots.
Skills Overview
/pulse - Map Current Design
Take the pulse of a system - what decisions define how it works TODAY.
# Start with a goal
deciduous add goal "API rate limiting behavior" -c 90
# Map options (possible approaches from the goal)
deciduous add option "Identify users by auth token" -c 85
deciduous link 1 2 -r "possible_approach"
deciduous add option "Use IP-based rate limiting" -c 85
deciduous link 1 3 -r "possible_approach"
Output: Decision tree of the current model (goal -> options -> decisions).
/narratives - Understand Evolution
Understand how the system evolved. Narratives are conceptual, not tied to commits.
- Look at the current system
- Ask "how did this get this way?"
- Infer narratives from the design
- Find evidence (commits, PRs, docs)
- Identify pivots - where the model changed
Output: .deciduous/narratives.md with evolution stories.
/archaeology - Structure for Query
Transform narratives into a queryable graph.
| Narrative Element | Graph Node |
|---|---|
| Title | goal |
| Possible approach | option |
| Choosing an approach | decision |
| What was learned | observation |
| PIVOT | revisit |
Output: Connected graph with Now ← revisit ← History.
Slash Commands
All slash commands are bootstrapped by deciduous init and updated by deciduous update.
| Command | Purpose |
|---|---|
/decision |
Manage decision graph - add nodes, link edges, sync |
/recover |
Recover context from decision graph on session start |
/work |
Start a work transaction - creates goal node before implementation |
/document |
Generate comprehensive documentation for a file or directory |
/build-test |
Build the project and run the test suite |
/serve-ui |
Start the decision graph web viewer |
/sync-graph |
Export decision graph to GitHub Pages |
/decision-graph |
Build a decision graph from commit history (archaeology) |
/sync |
Multi-user sync - pull events, rebuild, push |
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.
- today Changed · -37 lines · +14 tokens per session 2859ea33f5a6
- 5d ago First seen · 921 lines · 7,353 tokens per session scan A 4a19498dab25
deciduous CLAUDE.md is an instructions file published in the GitHub repository notactuallytreyanastasio/deciduous (160 stars, last pushed today), licensed Apache-2.0. It adds 7,367 tokens to every session, about $0.0368 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to deciduous AGENTS.md, differing in 47 lines, and is treated as a copy.
Other instructions, from other repositories
cognirepo CLAUDE.md
Claude Code instructions for ashlesh-t/cognirepo, covering claude.md, key rules, session start sequence (run in this order), behavioral confirmation rule and personas (cognirepo-402, cognirepo-403).
aeon CLAUDE.md
Claude Code instructions for aeonfun/aeon, covering aeon, how aeon works, strategy, voice and soul file hierarchy (read in this order).
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
mcp-structured-memory CLAUDE.md
Claude Code instructions for nmeierpolys/mcp-structured-memory, a project described as: Structured Memory MCP Server.
inkwell-memory CLAUDE.md
Instructions for veronchenko/inkwell-memory, covering claude.md — inkwellmemory, layout, multi-tenant mode (inkwellmultitenant=1), conventions and testing.
memory-mcp-1file AGENTS.md
Instructions for pomazanbohdan/memory-mcp-1file, covering ⛔ l0 invariants (never violate under any circumstance), detection heuristic, 🔀 phase transition routing (⛔ blocking), gate-0: phase identification & loading and 🧾 proof-of-load requirement (critical).