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 Jamie-BitFlight/claude_skills --skill topic-specialistgit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/topic-specialist)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/topic-specialist"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/topic-specialist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/topic-specialist"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/topic-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.00933 |
| Opus 5.5 | $0.00027 | $0.00373 |
| Sonnet 5.5 | $0.00014 | $0.00187 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
topic-specialist 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 22d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Topic Specialist
Answer the user's concrete technical question from evidence strong enough for the claim being made. Treat training-data recall as a hypothesis generator, not evidence.
Resolve the research contract
Before researching, identify:
- topic — the technology, library, system, protocol, or tool;
- question — the decision or fact to resolve;
- conditions — version, platform, configuration, environment, or other constraints that could change the answer;
- deliverable — answer only, or an explicitly requested update to an existing skill.
Infer these from the request when unambiguous. Ask only for missing information that could materially change the research result.
If the user identifies relevant skills or repository guidance, read them as domain context. Treat their factual claims as leads unless their authority independently establishes the claim.
Research
Choose the cheapest evidence capable of resolving the question. Do not mechanically inspect a repository README, entry point, and issue tracker when those sources cannot affect the answer.
Prefer evidence according to the claim:
| Claim | Strong evidence |
|---|---|
| Public API/configuration contract | Current official documentation/specification |
| Actual implementation behavior | Version-pinned source code and tests |
| Version/release behavior | Release notes/changelog plus version-pinned implementation when needed |
| Known defect or maintainer intent | Maintainer issue/discussion linked to the affected version |
| Runtime/environment behavior | Reproducible execution in the relevant environment |
| Historical rationale | Primary design/issue/commit evidence when available |
Use secondary sources for discovery, comparison, or when primary evidence is unavailable. Label the limitation rather than presenting weaker evidence as primary.
Keep the researched revision/version and environment explicit when they bound the finding.
Build claim evidence
For each material conclusion:
What ships with it
2 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.
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.
- 22d ago First seen · 99 lines · 68 tokens per session scan A 1fbe077ea49e
topic-specialist is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 933 once invoked, about $0.0003 per session on Opus 5.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-09-25.
Other skills, from other repositories
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…
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…
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…