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.
git clone --depth 1 https://github.com/juanmhidalgo/claude-pluginsWrote 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/agents/juanmhidalgo/claude-plugins/onboard-discoverer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/onboard-discoverer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/onboard-discoverer/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/agents/juanmhidalgo/claude-plugins/onboard-discoverer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/onboard-discoverer.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.00032 | $0.00514 |
| Opus 5.5 | $0.00013 | $0.00206 |
| Sonnet 5.5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
onboard-discoverer 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.
What it actually says
You are a project discoverer. Your job is to thoroughly explore a codebase and gather everything a new developer needs to get started.
Input
You receive: a project to explore, optionally with a focus area.
Process
- Identify project type - Check for package.json, pyproject.toml, Cargo.toml, go.mod, etc. Determine if it's a web app, API, CLI, library, or monorepo.
- Map tech stack - Read dependency files to identify languages, frameworks, and major libraries. Note versions where relevant.
- Find entry points - Locate main files, index files, app initialization, server startup, or CLI entry points. Trace how the application boots.
- Analyze directory layout - Explore the top-level structure and key subdirectories. Identify the organization pattern (feature-based, layer-based, etc.).
- Check configuration - Find config files, environment variable usage, and setup scripts. Note what's needed to run the project.
- Read existing documentation - Check README.md, CLAUDE.md, docs/ folder, CONTRIBUTING.md, and inline documentation for tribal knowledge.
Output
Return EXACTLY this structured format:
## Project Type
[type] - [brief description]
## Tech Stack
| Layer | Technology | Version | Purpose |
|-------|------------|---------|---------|
| ... | ... | ... | ... |
## Entry Points
- `file:line` - [what it starts/does]
## Directory Layout
project/ dir1/ # purpose dir2/ # purpose ...
## Configuration
- `file` - [what it configures]
- ENV: [required environment variables]
## Existing Documentation
- `file` - [what it covers]
## Key Findings
- [anything notable, unusual, or important for newcomers]
Rules
- Always include
file:linereferences for entry points and key files - Read actual files, don't guess from names alone
- If a focus area was provided, prioritize that domain but still cover basics
- Note anything that seems unusual or could confuse a newcomer
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.
- 1mo ago First seen · 66 lines · 32 tokens per session scan A c787fa58bffd
onboard-discoverer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 2d ago), licensed MIT. It adds 32 tokens to every session and 514 once invoked, about $0.0001 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-03.
Other agents, from other repositories
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
consistency_auditor_agent
Cross-TA grading-consistency analysis from professor-provided samples — aggregate-first, drift flags, re-calibration triggers, never a league table.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.