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/raisedadead/claude-code-plugins/tiger-stylenpx skills add raisedadead/claude-code-plugins --skill tiger-stylegit clone --depth 1 https://github.com/raisedadead/claude-code-pluginsWhat 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.00065 | $0.02423 |
| Opus 5 | $0.00032 | $0.01211 |
| Sonnet 5 | $0.00013 | $0.00485 |
| Haiku 4.5 | $0.00006 | $0.00242 |
Grade A, and why
tiger-style 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tiger-style — one shape rule computed, the rest read by hand
One TIGER_STYLE rule is cheap to compute from a diff; the rest need a reader. This skill keeps the two halves apart and labelled — a checklist presented as a gate is worse than no gate.
When to use
- Before committing a change that adds source lines.
- When a build reports
TIGER: BLOCKorTIGER: NAGand you need to know which limit applied. - When reviewing someone else's diff for shape rather than correctness.
Run the check
python3 "${CLAUDE_PLUGIN_ROOT}"/skills/tiger-style/scripts/tiger_check.py [repo-path]
Reads the staged diff (git diff --cached), never HEAD. --cached compares HEAD against the index, which is exactly what the commit will contain. HEAD would compare against the working tree instead: it would flag unstaged edits the commit does not carry, and it fails outright in a repository with no commits yet — a failure the checker would read as "nothing was added".
Only lines the change adds are measured. Existing long lines are somebody else's commit.
| exit | signal | meaning |
|---|---|---|
| 0 | TIGER: CLEAN <n> file(s)[, <m> skipped] |
no added line is over its limit, across the <n> files examined; <m> more were staged but not measured |
| 1 | TIGER: BLOCK <n> |
<n> added lines exceed a limit the repo declared |
| 2 | TIGER: NAG <n> |
<n> added lines exceed the built-in 100-column fallback |
| 64 | — | the path is not a git work tree |
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 · 100 lines · 65 tokens per session scan A 19dde16addae
tiger-style is a skill published in the GitHub repository raisedadead/claude-code-plugins (2 stars, last pushed 7d ago), licensed ISC. It adds 65 tokens to every session and 2,423 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-31.
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…