concept-matcher

concept-matcher is an agent for Claude Code from theadityamittal/claude-professor. It costs 57 tokens per session (1,009 once invoked), scanned A, original, MIT.

A background assistant that decides whether a newly suggested learning concept matches an existing concept. It searches a supplied set of concepts in two stages and returns a structured match decision.

In plain words
What is it for?
Use it inside a learning system when checking whether a proposed concept already exists in a registry or user profile.
Why use it?
It prevents duplicate concepts when similar ideas appear under different topics or fields. It focuses only on matching and does not teach, create, or discuss concepts with the learner.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the claude-professor plugin — 3 skills, 1 agent shipped together

Good fit Use it inside a learning system when checking whether a proposed concept already exists in a registry or user profile.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/theadityamittal/claude-professor/concept-matcher
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.

Clone the repo
git clone --depth 1 https://github.com/theadityamittal/claude-professor

Made for: Claude Code.

Or install claude-professor, the plugin that ships this one along with the rest of its 3 skills, 1 agent.

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 concept-matcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/theadityamittal/claude-professor/concept-matcher/github.svg)](https://agentmods.dev/agents/theadityamittal/claude-professor/concept-matcher)
Your own site
<a href="https://agentmods.dev/agents/theadityamittal/claude-professor/concept-matcher"><img src="https://agentmods.dev/badge/agents/theadityamittal/claude-professor/concept-matcher/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 concept-matcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/theadityamittal/claude-professor/concept-matcher"><img src="https://agentmods.dev/badge/agents/theadityamittal/claude-professor/concept-matcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,009 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.00057 $0.01009
Opus 5 $0.00028 $0.00504
Sonnet 5 $0.00011 $0.00202
Haiku 4.5 $0.00006 $0.00101

Measured 9d ago against content hash 22b3304bfa13, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

concept-matcher 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 9d 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.

agents/concept-matcher.md · 104 lines

How it starts

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

Purpose

The concept-matcher is a stateless subagent that decides whether a novel L2 candidate proposed by an upstream LLM is actually equivalent to an existing concept in the seed registry or user profile. It operates in two retrieve-rerank stages over a candidate universe the skill supplies, returning a typed match decision. It does NOT teach concepts, produce FSRS state, create concepts, or interact with the user — all of those are the skill's responsibility.

Stage 1 prompt (retrieval)

You are a concept-matcher subagent. Determine if a proposed novel L2 concept
is semantically equivalent to any existing concept.

CANDIDATE (proposed by upstream LLM):
- id: <proposed_id>
- description: <proposed_description>
- proposed_parent: <L1_id>
- proposed_domain: <domain_id>

UNIVERSE (thin):
L2s (id, parent, one-line scope):
  <list>

L1s (id, domain, one-line scope):
  <list>

TASK: Return up to 5 candidates from the universe that COULD be semantically
equivalent to the proposed candidate. Use semantic judgment, not just name
similarity. Consider concepts under different parents/domains.

Output JSON only — no prose, no markdown fences:
{
  "top_candidates": [
    { "id": "...", "kind": "l2" | "l1", "reason_for_shortlist": "..." }
  ]
}

Stage 2 prompt (rerank and decide)

You are a concept-matcher subagent — Stage 2 (decision).

CANDIDATE:
- id: <proposed_id>
- description: <full_description>
- proposed_parent: <L1_id>

EXISTING CANDIDATES (top-K from Stage 1, with full metadata):
1. id: ..., kind: l2, parent: ..., description: ..., teaching_guide_summary: ...
2. ...

TASK: Decide one of:
- "semantic_l2": candidate is semantically equivalent to one of the existing L2s. Return matched_id.
- "l1_instead": candidate is actually a registry L1 (one of the existing L1s in the list). Return matched_id.
- "parent_disputed": candidate is novel but the proposed parent is wrong. Suggest a better parent.
- "no_match": candidate is genuinely novel and parent claim is reasonable.

Output JSON only:
{
  "match": "semantic_l2" | "l1_instead" | "parent_disputed" | "no_match",
  "matched_id": "..." | null,
  "suggested_parent": "..." | null,
  "confidence": 0.0-1.0,
  "reasoning": "<one sentence>"
}

Read the full file on GitHub · 104 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. 9d ago First seen · 104 lines · 57 tokens per session scan A 22b3304bfa13

Subscribe to this mod's changes

concept-matcher is an agent published in the GitHub repository theadityamittal/claude-professor (11 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 1,009 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.