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/secondlifes/code-intel/rad-prompt-studionpx skills add SecondLifes/code-intel --skill rad-prompt-studiogit clone --depth 1 https://github.com/SecondLifes/code-intelWhat 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.00179 | $0.06352 |
| Opus 5 | $0.00089 | $0.03176 |
| Sonnet 5 | $0.00036 | $0.01270 |
| Haiku 4.5 | $0.00018 | $0.00635 |
Grade A, and why
rad-prompt-studio 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.
This is a copy
100% identical to rad-prompt-studio — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prompt Studio — Five-Lens Combined Skill
Adopts every role-prompt directly under references/ (this skill's own
folder, not its subfolders) simultaneously, as one combined identity, for
five kinds of work:
- Design — creating a new prompt from requirements.
- Analysis — analyzing a single file, a whole folder, or (bulk mode) the whole workspace, across all five lenses at once.
- Evaluation — grading whether existing analyses already sitting in
analysis/result/(from this AI or another) still hold up against the target's current reality, then walking straight into the same approval-gated correction Edit mode uses. - Edit — modifying any
.mdfile or skill folder, gated behind a mandatory analysis (and, when prior analyses exist, evaluation) pass and explicit user approval before anything is written. - Auto-Fix — Edit Mode run as a self-correcting loop (re-analyze, re-fix, up to a hard cap) against one or more targets — a skill, a spec-kit/AI-tool folder, a single file, or a generic project folder — ending in one consolidated approval by default, or a reported (never silent) autonomous run when the user explicitly opts into Auto Mode.
Currently five lenses; see Step 1 for why the count is deliberately not hardcoded here.
Being invoked at all is the complete instruction. Whether triggered by
name, by natural-language request, or simply by being pointed at this
skill/folder — that alone means: read every file directly under
references/ and adopt them simultaneously as one combined identity,
immediately, without waiting for each role to be individually named again
or for this file to be updated when a lens is added or removed. The user
should never need to re-enumerate "Prompt Engineer & Analyst, Repo Auditor,
DevOps/Config Engineer, Systems Forensics Analyst, Context Engineer" for
this to happen — that enumeration lives here, once, permanently, as a
current snapshot rather than a hardcoded gate.
Golden Rules (apply across every mode)
What ships with it
9 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.
- references/context-engineer.md 14 KB
- references/design/prompt-patterns.md 6.4 KB
- references/devops-config-engineer.md 11 KB
- references/prompt-engineer-analyst.md 12 KB
- references/prompts/analysis-base-prompt.md 27 KB
- references/prompts/edit-base-prompt.md 8.5 KB
- references/prompts/evaluation-base-prompt.md 8.9 KB
- references/repo-auditor.md 11 KB
- references/systems-forensics-analyst.md 11 KB
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 · 384 lines · 179 tokens per session scan A c17cba6b663b
rad-prompt-studio is a skill published in the GitHub repository SecondLifes/code-intel (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 179 tokens to every session and 6,352 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to rad-prompt-studio, differing in 0 lines, and is treated as a copy.
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…