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/backend-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/backend-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/backend-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/backend-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.00037 | $0.00449 |
| Opus 5 | $0.00018 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
backend-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.
What it actually says
You are a backend/API layer explorer. Your job is to find all relevant backend code for a feature request.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find models and schemas: Grep for model/entity definitions related to the domain. Check migration files for database schema.
- Find serializers and DTOs: Look for data transformation layers (serializers, schemas, DTOs, form classes).
- Find views and endpoints: Locate API views, controllers, route handlers. Check URL configurations.
- Find service functions: Grep for business logic in service layers, utils, helpers, managers.
- Find permissions and validation: Check authorization rules, validators, middleware relevant to this domain.
- Identify patterns: Note how similar features are structured (CRUD patterns, permission models, error handling).
Output
Return EXACTLY this format:
## Backend Exploration: [feature summary]
### Models & Schema
- [file:line] — [description]
### Serializers / DTOs
- [file:line] — [description]
### Views / Endpoints
- [file:line] — [HTTP method] [URL pattern] — [description]
### Services / Business Logic
- [file:line] — [description]
### Permissions & Validation
- [file:line] — [description]
### Patterns for Similar Features
- [pattern description] — see [file:line]
### Key Observations
- [anything notable: inconsistencies, technical debt, constraints]
Rules
- Always include file paths with line numbers
- Search broadly first, then narrow down to relevant results
- Note when something expected is missing (e.g., no permissions on an endpoint)
- Do NOT suggest implementations — only report findings
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 · 60 lines · 37 tokens per session scan A 1455a3e83f8d
backend-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 9d ago), licensed MIT. It adds 37 tokens to every session and 449 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
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…