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 skills/notactuallytreyanastasio/deciduous/pulsenpx skills add notactuallytreyanastasio/deciduous --skill pulsegit 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/pulse)<a href="https://agentmods.dev/skills/notactuallytreyanastasio/deciduous/pulse"><img src="https://agentmods.dev/badge/skills/notactuallytreyanastasio/deciduous/pulse.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.00014 | $0.00477 |
| Opus 5 | $0.00007 | $0.00238 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
pulse 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 5d 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
Pulse
Map the current model as decisions. No history, just now.
Step 1: Get current state
deciduous pulse
Review the report: active goals, coverage gaps, orphan nodes. This tells you what's already mapped and what needs attention.
Step 2: Pick a scope
What part of the system are you taking the pulse of?
- A feature ("Suspense fallback behavior")
- A subsystem ("Authentication")
- A boundary ("API request lifecycle")
Step 3: Ask "What decisions define this?"
Read the code. For the thing you're scoping, ask:
"What design questions had to be answered for this to work?"
Not implementation questions ("which library?") - model questions ("what's the behavior?")
Step 4: Build the goal -> options -> decisions
# Create the root goal
deciduous add goal "<Scope>: <Core question>" -c 90
# Add options (possible approaches from the goal)
deciduous add option "<Possible approach>" -c 85
deciduous link <goal> <option> -r "possible_approach"
# When an option is chosen, create a decision
deciduous add decision "Chose <approach>" -c 90
deciduous link <option> <decision> -r "chosen"
If a question is still open, leave it as option nodes without a decision.
Step 5: Review
deciduous pulse
deciduous pulse --summary
deciduous serve
Check for Supporting Documents
deciduous doc list <goal_id>
deciduous doc attach <goal_id> docs/architecture.png -d "Current architecture"
Decision Criteria
- Worth capturing? Does it define BEHAVIOR, not implementation?
- How deep? Stop when decisions become implementation details
- Option vs Decision? Option = possible approach. Decision = choosing which option.
Connecting to History
Pulse gives you the "Now". For history, run /narratives then /archaeology.
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.
- 5d ago First seen · 76 lines · 14 tokens per session scan A 82ddb615f712
pulse is a skill published in the GitHub repository notactuallytreyanastasio/deciduous (160 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 477 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…