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/microsoft/shadowfrog/shadow-frog-dreamnpx skills add microsoft/ShadowFrog --skill shadow-frog-dreamgit clone --depth 1 https://github.com/microsoft/ShadowFrogWhat 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.00106 | $0.12545 |
| Opus 5 | $0.00053 | $0.06273 |
| Sonnet 5 | $0.00021 | $0.02509 |
| Haiku 4.5 | $0.00011 | $0.01255 |
Grade B, and why
shadow-frog-dream scanned grade B with 1 finding 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 2d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`rm -rf` if `git worktree remove` silently fails — the failure mode that Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 1,208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShadowFrog Dream
Autonomous experimentation while the user is away. Every task is an experiment — implement real code in a worktree, run it, persist as a named git branch pushed to a remote the user can write to. Dream's unique value is implementation experience that compounds across sessions.
Critical Invariants
These rules are stated ONCE here and enforced by helper scripts. Violating any of them is a completion criteria failure.
Prerequisite: .shadow/ must be git-tracked
Dream moves .shadow/ content through git — artifacts are committed onto
the dream branch, pushed to the remote, then read back by the reconciler via
git show origin/<branch> .shadow/.... If .shadow/ is gitignored (the
"local only" option in shadow-frog-init), git add -A silently skips those
files, nothing reaches the remote, and the reconciler finds no manifest —
every discovery is lost without warning. dream-setup.sh runs
git check-ignore .shadow up front and refuses to start if it's ignored.
Use shadow-frog-update instead for local-only shadows.
Path Isolation
WORKTREE_BASE = /tmp/shadowfrog-dreams/<DREAM_NS>/
WORKTREE_DIR = $WORKTREE_BASE/dream-<SLUG>
- Worktrees are ALWAYS in
/tmp/shadowfrog-dreams/<DREAM_NS>/, NEVER in the project directory. This prevents conflicts between parallel agents and keeps the main repo clean. DREAM_NS(namespace) isolates branches per task/instance. Resolved from:DREAM_NAMESPACEenv →TASK_INFO.json→.env→ repo basename.- Override only with
DREAM_WORKTREE_BASEenv var if/tmpis too small. dream-setup.shcomputes and enforces all paths. Use it.
Branch Naming
BRANCH_NAME = dream/<DREAM_NS>/<DREAM_ID>
DREAM_ID = YYYYMMDD-HHMMSSZ-<SLUG>
Artifact Format
.shadow/_dreams/<DREAM_ID>/report.md
.shadow/_dreams/<DREAM_ID>/manifest.json
.shadow/_dreams/<DREAM_ID>/patch.diff
NEVER flat files (_dreams/<DREAM_ID>.md). Flat files break the pipeline.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 1,208 lines · 106 tokens per session scan B 2ba12893d226
shadow-frog-dream is a skill published in the GitHub repository microsoft/ShadowFrog (21 stars, last pushed 13d ago), licensed MIT. It adds 106 tokens to every session and 12,545 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
paperclip
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
add-resend
Add Resend (email) channel integration via Chat SDK.
codegen
Code generation utilities for json-render. Use when generating code from UI specs, building custom code exporters, traversing specs, or serializing props for @json-render/codegen.
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
optimize-agentic-workflow
Analyze and reduce token consumption in agentic workflows — guardrail-specific entry points, measurement, and optimization techniques.