recommend-experts

recommend-experts is a skill for Claude Code from rojim666/SztuCode. It costs 47 tokens per session (655 once invoked), scanned A, original, MIT.

A workflow for finding and recommending specialist AI experts or expert teams when a task needs professional judgement or research. It checks that no expert is already selected before making a recommendation.

In plain words
What is it for?
Use it to recommend up to three relevant experts or teams for research, specialist work, or tasks needing several roles.
Why use it?
It helps users find a suitable specialist instead of handling a complex task with a general assistant alone. It also avoids replacing an expert that is already active.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to recommend up to three relevant experts or teams for research, specialist work, or tasks needing several roles.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rojim666/sztucode/recommend-experts
Install

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.

Any agent
npx skills add rojim666/SztuCode --skill recommend-experts
Clone the repo
git clone --depth 1 https://github.com/rojim666/SztuCode

Made for: Claude Code.

Wrote 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.

agentmods badge for recommend-experts

README.md
[![agentmods](https://agentmods.dev/badge/skills/rojim666/sztucode/recommend-experts/github.svg)](https://agentmods.dev/skills/rojim666/sztucode/recommend-experts)
Your own site
<a href="https://agentmods.dev/skills/rojim666/sztucode/recommend-experts"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/recommend-experts/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.

agentmods 80×15 button for recommend-experts

Your own site · 80×15
<a href="https://agentmods.dev/skills/rojim666/sztucode/recommend-experts"><img src="https://agentmods.dev/badge/skills/rojim666/sztucode/recommend-experts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00655
Opus 5.5 $0.00019 $0.00262
Sonnet 5.5 $0.00009 $0.00131
Haiku 4.5 $0.00005 $0.00065

Measured 1mo ago against content hash 0481a4d3f335, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

recommend-experts 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 1mo 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.

packages/runtime-ts/prompts/Sztubuddy/skills/recommend-experts/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Recommend Experts

Use this Skill only when a specialist role or multi-role workflow would clearly improve the current task and no Expert is selected in the current session.

Workflow

  1. Confirm that no Expert is selected in the current session. If one is already selected, stop immediately; do not search, recommend, or replace it.
  2. Call search_plugins with type set to expert. Put the user's request in userIntent; add keywords only when useful.
  3. Match the current task against the curated scenarios and candidate descriptions. Candidates may be individual expert plugins or expert_team plugins; select at most three in total.
  4. Every plugin ID must exactly match an id returned by this search_plugins call.
  5. Call suggest_plugin_install exactly once to render one Expert card. If recommending multiple candidates, include all of them in this single call:
{
  "type": "expert",
  "contextLabel": "For this deep-research task",
  "pluginId1": "DeepResearchExpert",
  "pluginId2": "GPTResearcherTeam"
}

suggest_plugin_install Schema

Follow this schema exactly:

{
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "type": {
      "type": "string",
      "enum": ["connector", "expert"]
    },
    "contextLabel": {
      "type": "string"
    },
    "pluginId1": { "type": "string" },
    "pluginId2": { "type": "string" },
    "pluginId3": { "type": "string" }
  },
  "required": ["type", "pluginId1"]
}

One call can recommend at most three candidates. Never pass arrays, plugins, pluginIds, or an { "item": ... } wrapper.

Rules

  • Never invoke suggest_plugin_install more than once in the same response, whether sequentially or in parallel.
  • A single suggest_plugin_install call can recommend one to three candidates by using pluginId1, pluginId2, and pluginId3.
  • The user can enable only one Expert or Expert Team; never enable one silently or replace the current Expert.
  • Do not replace the suggest_plugin_install card with a text list.
  • If the search returns expertAlreadySelected: true, immediately continue the original task without recommending again.
  • If the search returns no relevant results, silently continue the original task.
  • After the user skips, times out, or cancels, do not recommend the same candidates again in the same response.
  • Never use web search to find Plugins; search_plugins is the only source for candidates.

Read the full file on GitHub · 67 lines

Changes

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.

  1. 1mo ago First seen · 67 lines · 47 tokens per session scan A 0481a4d3f335

Subscribe to this mod's changes

recommend-experts is a skill published in the GitHub repository rojim666/SztuCode (110 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 655 once invoked, about $0.0002 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-12.

Related

Other skills, from other repositories

codex-delegate

Delegate a coding task to the OpenAI Codex CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Codex — phrasings like "have Codex do X", "delegate this to Codex", "run it through Codex", or "use Codex to implement/fix/refactor" …

amElnagdy/delegate-skills · 155 tokens

commandcode-delegate

Delegate a coding task to the Command Code CLI (cmd) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Command Code — phrasings like "have Command Code do X", "delegate this to commandcode", "run it through cmd", or "use Command Code…

amElnagdy/delegate-skills · 123 tokens

claude-delegate

Delegate a coding task to a separate Claude Code CLI process or another Claude session as an implementer, then review its diff and land it yourself. Use only when the user explicitly asks to delegate implementation to Claude Code, another Claude session, or the claude CLI — for example, "have another Claude implement…

amElnagdy/delegate-skills · 117 tokens

copilot-delegate

Delegate a coding task to the GitHub Copilot CLI (copilot) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Copilot - phrasings like "have Copilot implement X", "delegate this to copilot", "run it through Copilot CLI", or "use…

amElnagdy/delegate-skills · 129 tokens

cursor-delegate

Delegate a coding task to the Cursor Agent CLI (cursor-agent) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Cursor — phrasings like "have Cursor implement X", "delegate this to Cursor", "run it through Cursor Agent", or "use…

amElnagdy/delegate-skills · 120 tokens

cline-delegate

Delegate a coding task to the Cline coding agent CLI (cline) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Cline - phrasings like "have Cline implement X", "delegate this to cline", "run it through Cline", or "use cline to…

amElnagdy/delegate-skills · 126 tokens