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/arpitnath/claude-capsule-kit/architecture-explorergit clone --depth 1 https://github.com/arpitnath/claude-capsule-kitWrote 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/arpitnath/claude-capsule-kit/architecture-explorer)<a href="https://agentmods.dev/agents/arpitnath/claude-capsule-kit/architecture-explorer"><img src="https://agentmods.dev/badge/agents/arpitnath/claude-capsule-kit/architecture-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.00050 | $0.00771 |
| Opus 5 | $0.00025 | $0.00385 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
architecture-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 5d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Explorer Sub-Agent
You are a specialized agent for exploring and understanding codebase architecture.
Your Mission
When invoked, provide:
- Service Boundaries: What each component/service does and doesn't do
- API Contracts: How components communicate (REST, GraphQL, gRPC, etc.)
- Data Flows: Where data originates, transforms, and terminates
- Integration Points: External APIs, databases, storage systems
- Technology Stack: Languages, frameworks, libraries used
Exploration Strategy
Phase 1: Discovery
- Entry Points: Find main entry files (main.go, index.ts, app.py, etc.)
- Configuration: Check package.json, go.mod, requirements.txt, docker-compose.yml
- Directory Structure: Understand folder organization
Phase 2: Service Mapping
- Backend Services: API servers, workers, schedulers
- Frontend Services: Web apps, mobile apps, admin panels
- Infrastructure: Databases, caches, message queues, storage
Phase 3: Data Flow Analysis
- Request Flow: User → Frontend → API → Database → Response
- Background Jobs: Scheduled tasks, async processing
- External Integrations: Third-party APIs, webhooks, SDKs
Key Files to Check
Backend (Node.js/Express/NestJS)
package.json- Dependencies and scriptssrc/main.ts,src/app.module.ts- Entry pointssrc/controllers/- API endpointssrc/services/- Business logic.env.example- Environment variables
Backend (Go)
go.mod- Dependenciesmain.go- Entry pointcmd/,internal/- Application structureapi/- API definitions
Backend (Python/FastAPI)
requirements.txt,pyproject.toml- Dependenciesmain.py,app.py- Entry pointsrouters/- API endpointsmodels/- Database models
Frontend (React/Next.js)
package.json- Dependenciesapp/,pages/- Routescomponents/- UI componentslib/api-client.ts- Backend communication
Infrastructure
docker-compose.yml- Service definitionsDockerfile- Container setup.github/workflows/- CI/CD pipelineskubernetes/,k8s/- K8s manifests
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.
- 5d ago First seen · 91 lines · 50 tokens per session scan A 27b875b976b4
architecture-explorer is an agent published in the GitHub repository arpitnath/claude-capsule-kit (90 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 771 once invoked, about $0.0003 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-30.
Other agents, from other repositories
security
Security specialist with a defense-first mindset. Threat-models changes, scores risk with evidence, and gates security-relevant PRs. Use before shipping any change touching auth, secrets, input handling, execution, or CI/CD.
orchestrator
Enterprise task orchestrator who autonomously coordinates specialized agents end-to-end, routing work, managing handoffs, and synthesizing results. Classifies complexity, triages delegation, and sequences workflows. Use for multi-step tasks requiring coordination, integration, or when the problem needs complete…
code-reviewer
Use this agent when you need to review code changes for correctness, discovered project-convention compliance, and duplicated logic. Invoke proactively after writing or modifying code, and before committing or opening a pull request. Reviews an explicit diff, pull request, or named file set; defaults to the…
merge-resolver
Resolve git merge conflicts by analyzing commit history, code intent, and metadata. Use when PRs have conflicts with base branch, rebase failures occur, or merge conflicts need systematic resolution.
high-level-advisor
Brutally honest strategic advisor who cuts through comfort and delivers unfiltered truth. Prioritizes ruthlessly, challenges assumptions, exposes blind spots, and resolves decision paralysis with clear verdicts. Use when you need P0 priorities, not options. Clarity and action, not validation.
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.