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 skills add michal-bajer1/shadow --skill load-decisionsgit clone --depth 1 https://github.com/michal-bajer1/shadowWrote 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/michal-bajer1/shadow/load-decisions)<a href="https://agentmods.dev/skills/michal-bajer1/shadow/load-decisions"><img src="https://agentmods.dev/badge/skills/michal-bajer1/shadow/load-decisions.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.1 | $0.00043 | $0.00415 |
| Opus 5 | $0.00022 | $0.00208 |
| Sonnet 5 | $0.00009 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
load-decisions 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 7d 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
Run:
shadow-cli query --all
where is the file or directory you are about to work on.
If the command returns results, read them before proceeding. Pay attention to:
- constraints: rules you must respect, regardless of what seems simpler
- decision: the established pattern — follow it unless you have a reason to supersede
- rejected: approaches already tried and discarded — do not re-propose these
- forward: unresolved threads you may need to address
- drift label: if the record is file-drift, struct-drift, or stale, run
shadow-cli diff <blob-sha> <path>to see what changed before deciding whether to confirm or supersede
If no prior decisions exist for the path, proceed without comment.
When to escalate to the session-orient agent
Delegate to the session-orient agent when any of these are true:
- You are starting work on an area for the first time this session AND multiple records exist with drift labels
- The path spans several directories with decisions recorded at different levels
- Multiple
forwardthreads appear that may affect what you are about to do - You are unsure whether drifted records still apply and need a fuller picture
To delegate:
Use the Agent tool with subagent_type "session-orient", passing the path(s) you are about to work on as context.
The agent will read drifted files in full, cross-reference recent git history, and return a brief that is more thorough than a raw query output.
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.
- 7d ago First seen · 46 lines · 43 tokens per session scan A 096bef444f6a
load-decisions is a skill published in the GitHub repository michal-bajer1/shadow (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 415 once invoked, about $0.0002 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.