berekvolgyipeter Agent Harness
Help users discover, explore, and understand agent harness frameworks and Claude Code resource collections from curated repositories.
Catalog
The catalog at ~/.claude/skills/agent-harness/references/catalog.json lists all indexed repositories with descriptions and topics. Read it first to understand what's available and which repo is most relevant to the user's need.
Each entry has these fields: github (source repo), local_path (where it's cloned), description (what it contains), topics (keyword tags), and content_types (e.g. agents, frameworks, resources).
All repos are cloned and indexed together under a single path:
~/.claude/skills-references/agent-harness/
Each repo lives at the local_path specified in the catalog (e.g., ~/.claude/skills-references/agent-harness/coleam00-archon/).
Search
Always start with semantic search — it combines semantic understanding with BM25 keyword matching, so it surfaces conceptually relevant results even when exact keywords differ. Only fall back to Grep if semantic search returns no results or the index is unavailable.
Primary — semantic search:
mcp__claude-context__search_code(
path="~/.claude/skills-references/agent-harness",
query="<user need>"
)
Fallback — keyword search (only when semantic search fails or is unavailable):
Grep(pattern="<keyword>", path="~/.claude/skills-references/agent-harness/", glob="*.md")
Browse
To list contents of a specific repo:
Glob(~/.claude/skills-references/agent-harness/<repo-dir>/**/*.md)
Check for structured metadata files if present:
Glob(~/.claude/skills-references/agent-harness/<repo-dir>/**/*manifest*.json)
Glob(~/.claude/skills-references/agent-harness/<repo-dir>/**/*config*.json)
Workflow
- Understand the need — ask clarifying questions if the user's request is vague (e.g., "agent" could mean orchestration framework, a specific Claude Code agent, or a resource collection).
- Catalog — read
~/.claude/skills/agent-harness/references/catalog.jsonto identify which repos are relevant based on descriptions and topics. - Search — use semantic search to find matching content across all repos.
- Read before recommending — read the relevant README, docs, or source files before presenting findings. Understand what it does, what dependencies it needs, and how to use it.
- Present matches — show name, description, source repo, and category. When multiple options exist, compare them briefly.
- Guide usage — explain how to run, configure, or integrate what was found. Point to setup docs, env vars, or prerequisites as needed.