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/artem-from-ua/claude-plugins/technology-explainer-setupnpx skills add artem-from-ua/claude-plugins --skill technology-explainer-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/technology-explainer-setup)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/technology-explainer-setup"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/technology-explainer-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.00055 | $0.00643 |
| Opus 5 | $0.00028 | $0.00321 |
| Sonnet 5 | $0.00011 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
technology-explainer-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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technology Explainer Setup
Configure how Claude adapts explanation depth based on your proficiency with each technology.
Steps
1. Educational intro
Explain the three proficiency levels to the user:
- Expert — You know this technology deeply. Claude gives brief, no-theory answers. Just the facts and commands.
- Intermediate — You use this technology regularly but in limited scope. Claude explains nuances, gotchas, and edge cases but skips the basics.
- Learning — You're actively studying this technology. Claude provides detailed theory, concrete examples, and step-by-step walkthroughs.
Explain that "technology" is broadly defined: operating systems (Linux, macOS), programming languages (Python, Java), tools (Docker, Git), platforms (AWS, GCP), workflows (CI/CD, Agile), and anything else the user works with.
2. Show existing config
Read ~/.claude/technology-explainer.json. If it exists, display the current configuration as a formatted table showing technologies grouped by level, the default level, and any configured sources. If it doesn't exist, say "No proficiency config found — let's create one."
3. Ask expert technologies
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you know deeply. Claude will give brief, no-theory answers."
Suggest common categories: operating systems, shells, languages, IDEs, version control.
4. Ask learning technologies
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you're actively studying. Claude will provide detailed theory, examples, and step-by-step explanations."
5. Ask intermediate technologies
Use AskUserQuestion with a free-text "Other" option. Remind the criteria: "Technologies you use regularly but in limited scope. Claude will explain nuances and gotchas but skip basics."
6. Ask default level
Use AskUserQuestion:
- Learning (Recommended) — detailed explanations for anything not listed
- Intermediate — nuanced explanations for unlisted technologies
- Expert — brief answers for everything not listed
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.
- 5d ago First seen · 60 lines · 55 tokens per session scan A 2147d20a1b2a
technology-explainer-setup is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 19d ago), licensed MIT. It adds 55 tokens to every session and 643 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…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…