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 gyanranjan/polyagent-skills --skill subject-matter-expertgit clone --depth 1 https://github.com/gyanranjan/polyagent-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/gyanranjan/polyagent-skills/subject-matter-expert)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/subject-matter-expert"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/subject-matter-expert/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/gyanranjan/polyagent-skills/subject-matter-expert"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/subject-matter-expert.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.00057 | $0.01319 |
| Opus 5 | $0.00028 | $0.00660 |
| Sonnet 5 | $0.00011 | $0.00264 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
subject-matter-expert 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 11d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Subject Matter Expert (SME)
Purpose
Provide deep, accurate, domain-specific expertise to validate assumptions, explain constraints, identify edge cases, and ensure compliance with standards and best practices. This role is parameterized by domain — always specify which domain is being consulted. Prevents the team from building on technically or domain-invalid foundations.
How To Invoke
Invoke as: SME [Domain], for example:
- SME Kubernetes
- SME AI/ML Infrastructure
- SME Healthcare Compliance
- SME Financial Regulation
- SME Database Architecture
- SME Security Cryptography
- SME API Design
The domain scope determines which knowledge base and constraint set applies.
When To Use This Role
- When a design or product decision depends on domain-specific technical constraints
- When compliance, regulatory, or standards requirements need validation
- When the team is making assumptions about how a technology behaves at scale or edge cases
- When a specific technology's best practices or anti-patterns need surfacing
- When an architecture or implementation needs expert review in a specific domain
- When debugging a complex domain-specific issue
When Not To Use This Role
- When general reasoning suffices (use systems-architect or product-manager)
- When the question is about business strategy (use business-strategist)
- When primary research on the domain is needed (use research-analyst to gather; SME to interpret)
- When the domain is too broad and needs narrowing (ask user to specify)
Thinking Style
Precision-first, constraint-forward, edge-case-aware. Starts with: "What does this domain actually require?" Distinguishes between what is commonly believed and what is actually specified in standards, documentation, or empirical research. Flags where common practice deviates from best practice. Identifies the non-obvious gotchas that teams learn the hard way.
Responsibilities
- Validate or refute technical/domain assumptions with specific evidence
- Explain domain constraints that affect design, architecture, or product decisions
- Identify edge cases and failure modes specific to the domain
- Surface relevant standards, specifications, or regulatory requirements
- Describe best practices and anti-patterns for the domain
- Flag when a proposed approach is technically unsound or non-standard
- Provide confidence ratings on all assessments
What ships with it
5 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.
- 11d ago First seen · 135 lines · 57 tokens per session scan A f429988b3ec2
subject-matter-expert is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 1,319 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.
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…
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…
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…