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/agents-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/agents-md)<a href="https://agentmods.dev/instructions/notactuallytreyanastasio/deciduous/agents-md"><img src="https://agentmods.dev/badge/instructions/notactuallytreyanastasio/deciduous/agents-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.07066 | $0.07066 |
| Opus 5 | $0.03533 | $0.03533 |
| Sonnet 5 | $0.01413 | $0.01413 |
| Haiku 4.5 | $0.00707 | $0.00707 |
Grade A, and why
deciduous AGENTS.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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- deciduous CLAUDE.md — 95% identical, 47 lines differ
How it starts
The opening of the file, as written. The whole thing — 900 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Instructions for OpenCode
This file was converted from CLAUDE.md. OpenCode uses AGENTS.md for project instructions. See: https://opencode.ai/docs/rules/
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.
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.
- 4d ago First seen · 900 lines · 7,066 tokens per session scan A 15bca1afc1e5
deciduous AGENTS.md is an instructions file published in the GitHub repository notactuallytreyanastasio/deciduous (160 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7,066 tokens to every session, about $0.0353 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.