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-initnpx skills add microsoft/ShadowFrog --skill shadow-frog-initgit 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.00063 | $0.02114 |
| Opus 5 | $0.00032 | $0.01057 |
| Sonnet 5 | $0.00013 | $0.00423 |
| Haiku 4.5 | $0.00006 | $0.00211 |
Grade A, and why
shadow-frog-init 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShadowFrog Init
Creates .shadow/ directory with symbol-organized shadow files for every
source file. Run once per repo. If .shadow/ exists, ask user to reset or skip.
Primary: Python Helper Script
The companion script shadow-init.py lives in the same directory as
this SKILL.md file. To find and run it:
# Project install (Copilot CLI):
python3 .github/skills/shadow-frog-init/shadow-init.py [options]
# Or for Claude Code:
python3 .claude/skills/shadow-frog-init/shadow-init.py [options]
IMPORTANT: Run from the repo/worktree root directory. The script
auto-detects the root via git rev-parse --show-toplevel, which returns
the correct root for regular repos AND worktrees. If auto-detection fails
(common when python is routed through Docker or the .git file points to
an inaccessible path), pass --root explicitly:
# If auto-detect fails, pass the root explicitly:
python3 .github/skills/shadow-frog-init/shadow-init.py --root "$(pwd)"
# In Docker wrapper scenarios (eval harness), git may not work inside
# the container. Use --root to bypass git detection:
python3 .github/skills/shadow-frog-init/shadow-init.py --root /testbed
Options
| Flag | Effect |
|---|---|
--root DIR |
Repository root (default: auto-detect via git) |
--reset |
Delete existing .shadow/ and recreate |
--dry-run |
Show what would be created without writing |
What it does
- Discovers source files via
git ls-files - Filters through
.shadow/.shadowignore(gitignore syntax) - Extracts symbols from each file (classes, functions, methods)
- Creates per-file shadow
.mdfiles with symbol headings - Creates
_index.md,_prefs.md,_meta/state.json,.shadowignore - Reports: files, symbols, languages detected
After running
Tell the user:
- "Edit
.shadow/.shadowignoreto exclude files that shouldn't be shadowed" - "Run
/shadow-frog-dreamfor autonomous exploration, or/shadow-frog-updateafter your next changes"
What ships with it
1 file 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 · 268 lines · 63 tokens per session scan A 2c2a8e053895
shadow-frog-init is a skill published in the GitHub repository microsoft/ShadowFrog (21 stars, last pushed 13d ago), licensed MIT. It adds 63 tokens to every session and 2,114 once invoked, about $0.0003 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…