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 artem-from-ua/claude-plugins --skill retroscope-setupgit clone --depth 1 https://github.com/artem-from-ua/claude-pluginsWrote 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/artem-from-ua/claude-plugins/retroscope-setup)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/retroscope-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/retroscope-setup.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.00065 | $0.00945 |
| Opus 5 | $0.00032 | $0.00473 |
| Sonnet 5 | $0.00013 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
retroscope-setup 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 6d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/retroscope:setup — Retroscope Configuration Wizard
Interactive wizard to configure the retroscope plugin for your environment and project.
What this command does
- Checks for existing configuration
- Asks setup questions via dialog
- Creates/updates config files
- Initializes storage repository if needed
- Shows next steps
Step 1: Check Existing Config
Read existing configs (show current values as defaults):
~/.claude/retroscope.json— user-level (global defaults).claude-plugin/retroscope.json— project-level (overrides)
Step 2: Ask Configuration Questions
Use AskUserQuestion to collect settings in this order:
- Storage directory — where to store reports. Suggest:
~/devel/retroscope. If doesn't exist: offer to create +git init. - Remote URL (optional) — detect GitHub username via
gh api user -q .login, offerhttps://github.com/{username}/retroscope, custom URL, or skip. - Report language — system default (recommended), English, or custom.
- Report generation model —
haiku(fastest, ~$0.01–0.03/report, recommended),sonnet(higher quality, ~$0.05–0.15/report), orinherit(current session model). - Extract mode — On (default, pre-filter to text-only, ~80–90% token reduction) or Off (full session data, ~5–10x more tokens, better for debugging insights).
- Session data source —
logs(default, reads full JSONL, reliable even after/compactor/clear) orcontext(current conversation, faster but may be incomplete). - Suggest /retro on exit? — Yes (default) or No.
- Auto-push reports? — No (default, commit locally only) or Yes.
- Report scope —
project(default, reports cover current project only) orall(cross-project daily reports aggregating sessions from all projects).
For full field descriptions and defaults, see ${SKILL_DIR}/references/config-schema.md.
Step 3: Write Config Files
User-level: ~/.claude/retroscope.json
{
"storageDir": "{chosen_path}",
"remoteUrl": "{remote_url_or_empty}",
"language": "{language}",
"timezone": "{detected_timezone}",
"model": "{haiku|sonnet|inherit}",
"extractMode": true,
"sessionSource": "logs",
"scope": "{project|all}",
"suggestRetroOnExit": true,
"autoPush": false
}
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.
- 6d ago First seen · 102 lines · 65 tokens per session scan A a05c261deca0
retroscope-setup is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 21d ago), licensed MIT. It adds 65 tokens to every session and 945 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…