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.
curl -O https://raw.githubusercontent.com/notactuallytreyanastasio/deciduous/main/.opencode/skills/narratives/SKILL.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/skills/notactuallytreyanastasio/deciduous/narratives)<a href="https://agentmods.dev/skills/notactuallytreyanastasio/deciduous/narratives"><img src="https://agentmods.dev/badge/skills/notactuallytreyanastasio/deciduous/narratives.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00016 | $0.00509 |
| Opus 5 | $0.00008 | $0.00254 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
narratives 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 8d 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.
What it actually says
Narrative Tracking
Narratives are the source of truth. Commits are just evidence.
Step 1: Initialize narratives file
deciduous narratives init
This creates .deciduous/narratives.md pre-populated with your active goal titles.
Step 2: Understand the system first
Before looking at git, read the code. Ask: What are the major pieces of this system?
Each major piece probably has a narrative behind it.
Step 3: Fill in the narratives
Edit .deciduous/narratives.md. For each section:
- Describe the current state (how it works today)
- Infer the evolution (how it likely got this way)
- Identify PIVOTs (when the conceptual model changed)
- Find evidence (PRs, commits, docs) - optional
- Check attached documents (
deciduous doc list)
Signs of a pivot:
- Two approaches coexisting (migration in progress)
- Comments explaining "we used to do X"
- Config for old + new system
- Deprecation warnings
Step 4: Review narratives
deciduous narratives show
Step 5: Check existing pivots
deciduous narratives pivots
Output Format
Each narrative section in .deciduous/narratives.md:
## <Name>
> <One sentence: what this piece of the system does>
**Current state:** <How it works today>
**Evolution:**
1. <First approach> - <why>
2. **PIVOT:** <what changed> - <why it changed>
3. <Current approach> - <why this is better>
**Evidence:** <Optional: PRs, commits, docs>
**Connects to:** <Other narratives this influenced>
**Status:** active | superseded | abandoned
What Makes a Good Narrative
- Coherent story about ONE design aspect
- Explains HOW something works and WHY it evolved
- Would help a new team member understand the system
- NOT a list of commits or feature changelog
Next Step
After narratives are written, run /archaeology to transform them into a queryable decision graph.
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.
- 8d ago First seen · 83 lines · 16 tokens per session scan A f27d703f66cc
narratives is a skill published in the GitHub repository notactuallytreyanastasio/deciduous (159 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 509 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 skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".