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/juanmhidalgo/claude-plugins/config-explorergit 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/config-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/config-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/config-explorer.svg" alt="Measured on agentmods" 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 | $0.00042 | $0.00710 |
| Opus 5 | $0.00021 | $0.00355 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
config-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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a configuration-surface explorer. Your job is to find all relevant config, environment, and feature-flag code for a feature request.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find config files: Glob for
.env*,settings.py,config/**/*.{ts,js,yaml,yml,toml,json},pyproject.toml,application.yml,application.properties,appsettings*.json. - Find env var reads: Grep for
process.env.,os.getenv,os.environ,import.meta.env.,Deno.env.get,viper.Get,System.getenv,ENV[. - Find typed-settings loaders: Look for
pydantic-settings/BaseSettings,dotenv,viper,config-rs,node-config,convict,zodenv schemas. - Find feature flags: Grep for LaunchDarkly (
ldclient,LDClient), GrowthBook, Unleash, Statsig, Optimizely, or in-repo flag modules (flags.py,featureFlags.ts,feature_flags/). - Find secrets handling: Look for vault clients (
hvac,@hashicorp/vault-client), AWS SSM/SecretsManager calls, GCP Secret Manager, Azure KeyVault,keyring, KMS usage. - Find per-environment overrides: Identify dev/staging/prod split patterns — directory layout, file naming (
config.dev.yaml), env-switch logic. - Find validation patterns: Where are config values validated at startup? How are missing/invalid values handled?
Output
Return EXACTLY this format:
## Config Exploration: [feature summary]
### Configuration Files
- [file] — [format, scope]
### Environment Variables Used in This Domain
- [VAR_NAME] — [file:line] — [purpose / default]
### Typed Settings / Loaders
- [file:line] — [library] — [what it loads]
### Feature Flags
- [flag name] — [file:line] — [provider] — [purpose]
### Secrets Handling
- [file:line] — [mechanism] — [what's stored]
### Per-Environment Overrides
- [pattern description] — see [file:line]
### Loading & Validation
- [where validation happens] — [file:line] — [strategy: fail-fast / lazy / silent]
### Key Observations
- [anything notable: missing validation, hardcoded values, env vars referenced but undocumented, secrets in plain config]
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.
- 4d ago First seen · 64 lines · 42 tokens per session scan A 70ac50200699
config-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 710 once invoked, about $0.0002 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.