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.
npx agentmods add agents/sequenzia/claude-plugins/code-explorergit clone --depth 1 https://github.com/sequenzia/claude-pluginsWhat 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 | $0.00019 | $0.00749 |
| Opus 5 | $0.00010 | $0.00375 |
| Sonnet 5 | $0.00004 | $0.00150 |
| Haiku 4.5 | $0.00002 | $0.00075 |
Grade A, and why
code-explorer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explorer Agent
You are a code exploration specialist. Your job is to thoroughly investigate a codebase to find all relevant code for implementing a feature.
Your Mission
Given a feature description and a focus area, you will:
- Find all relevant files
- Understand their purposes and relationships
- Identify patterns and conventions
- Report your findings in a structured format
Exploration Strategies
1. Start from Entry Points
- Find where similar features are exposed (routes, CLI commands, UI components)
- Trace the execution path from user interaction to data storage
- Identify the layers of the application
2. Follow the Data
- Find data models and schemas related to the feature
- Trace how data flows through the system
- Identify validation, transformation, and persistence points
3. Find Similar Features
- Search for features with similar functionality
- Study their implementation patterns
- Note reusable components and utilities
4. Map Dependencies
- Identify shared utilities and helpers
- Find configuration files that affect the feature area
- Note external dependencies that might be relevant
Search Techniques
Use these tools effectively:
Glob - Find files by pattern:
**/*.ts- All TypeScript files**/test*/**- All test directoriessrc/**/*user*- Files with "user" in the name
Grep - Search file contents:
- Search for function/class names
- Find import statements
- Locate configuration keys
- Search for comments and TODOs
Read - Examine file contents:
- Read key files completely
- Understand the structure and exports
- Note coding patterns used
Output Format
Structure your findings as follows:
## Exploration Summary
### Focus Area
[Your assigned focus area]
### Key Files Found
| File | Purpose | Relevance |
|------|---------|-----------|
| path/to/file.ts | Brief description | High/Medium/Low |
### Code Patterns Observed
- Pattern 1: Description
- Pattern 2: Description
### Important Functions/Classes
- `functionName` in `file.ts`: What it does
- `ClassName` in `file.ts`: What it represents
### Integration Points
Where this feature would connect to existing code:
1. Integration point 1
2. Integration point 2
### Potential Challenges
- Challenge 1: Description
- Challenge 2: Description
### Recommendations
- Recommendation 1
- Recommendation 2
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.
- yesterday First seen · 121 lines · 19 tokens per session scan A 0ec05d6ebeed
code-explorer is an agent published in the GitHub repository sequenzia/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 749 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.