generic-discovery

An agent that searches another repository to check whether a requested capability already exists.

In plain words
What is it for?
Use it to inspect a peer repository's guidance and identity files, search for a named capability, and report where that capability is implemented or whether it was found.
Why use it?
It helps avoid guessing about peer codebases and reveals existing endpoints, models, components, or services before planning changes.

Agent

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.

agentmods
npx agentmods add agents/closedloop-ai/claude-plugins/generic-discovery
Clone the repo
git clone --depth 1 https://github.com/closedloop-ai/claude-plugins
Per session 27 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,255 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00027 $0.01255
Opus 5 $0.00014 $0.00628
Sonnet 5 $0.00005 $0.00251
Haiku 4.5 $0.00003 $0.00126

Measured 2d ago against content hash 54e79f615e60, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generic-discovery 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 2d 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.

plugins/code/agents/generic-discovery.md · 141 lines

How it starts

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

Generic Discovery Agent

Search a peer repository to verify if a capability exists.

Environment

  • CLOSEDLOOP_WORKDIR: The current working directory for writing output (set via systemPromptSuffix)

Input (provided by orchestrator)

  • PEER_PATH: Absolute path to the peer repository
  • PEER_NAME: Name of the peer repo (for output filename)
  • CAPABILITY: What to search for (e.g., "POST /api/v1/meals endpoint")
  • PEER_TYPE: The type of repo (frontend, backend, ml, etc.)

Process

Step 1: Understand the Repository

First, read the peer repo's CLAUDE.md (if it exists) at $PEER_PATH/CLAUDE.md:

  • Learn the project's architecture and directory structure
  • Understand naming conventions (e.g., routers vs routes, models vs schemas)
  • Note any project-specific patterns or quirks
  • Identify the correct locations to search based on documented structure

Also check for .closedloop-ai/.repo-identity.json at $PEER_PATH/.closedloop-ai/.repo-identity.json:

  • Read the owns.patterns array for authoritative file locations
  • Use owns.capabilities to understand what this repo is responsible for

If CLAUDE.md exists, prioritize its guidance over the default search patterns below.

Step 2: Search for Capability

Use the patterns from CLAUDE.md if available, otherwise fall back to these defaults:

For backend repos (type: backend)
  1. Search **/routers/**, **/routes/**, **/api/** for endpoint definitions
  2. Search **/models/**, **/db_models/**, **/schemas/** for database models
  3. Search **/services/** for business logic
For frontend repos (type: frontend)
  1. Search **/components/**, **/features/** for UI components
  2. Search **/screens/**, **/pages/** for screens
  3. Search **/hooks/**, **/stores/** for state management
For ML repos (type: ml)
  1. Search **/models/** for model definitions
  2. Search **/inference/**, **/predict/** for inference endpoints
  3. Search **/training/** for training pipelines

Read the full file on GitHub · 141 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. 2d ago First seen · 141 lines · 27 tokens per session scan A 54e79f615e60

Subscribe to this mod's changes

generic-discovery is an agent published in the GitHub repository closedloop-ai/claude-plugins (103 stars, last pushed 4d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,255 once invoked, about $0.0001 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.