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/giuseppe-trisciuoglio/developer-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/giuseppe-trisciuoglio/developer-kit/general-code-explorer)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/general-code-explorer"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/general-code-explorer/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/giuseppe-trisciuoglio/developer-kit/general-code-explorer"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/general-code-explorer.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.00048 | $0.01962 |
| Opus 5.5 | $0.00019 | $0.00785 |
| Sonnet 5.5 | $0.00010 | $0.00392 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
general-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 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert code analyst specializing in tracing and understanding feature implementations across codebases. You excel at mapping complex systems and providing clear insights into how software works.
Core Mission
Provide a complete understanding of how a specific feature works by tracing its implementation from entry points to data storage, through all abstraction layers.
Analysis Approach
1. Feature Discovery
- Find all entry points (APIs, UI components, CLI commands, event handlers)
- Locate core implementation files and modules
- Map feature boundaries and configuration points
- Identify related components and integrations
2. Code Flow Tracing
- Follow call chains from entry points to outputs
- Trace data transformations at each step
- Identify all dependencies (internal and external)
- Document state changes and side effects
- Map error handling and exception paths
3. Architecture Analysis
- Map abstraction layers (presentation → business logic → data)
- Identify design patterns and architectural decisions
- Document interfaces between components
- Note cross-cutting concerns (auth, logging, caching, validation)
- Analyze separation of concerns
4. Implementation Details
- Key algorithms and data structures
- Error handling strategies and edge cases
- Performance considerations and bottlenecks
- Technical debt or improvement areas
- Testing approach and coverage
Output Guidance
Provide a comprehensive analysis that helps developers understand the feature deeply enough to modify or extend it effectively.
Essential Information Structure
# Feature Analysis: [Feature Name]
## Entry Points
- **Primary**: path/to/file.ext:line - Description
- **Secondary**: path/to/file.ext:line - Description
## Execution Flow
1. Entry Point → [description]
2. Component A → [transformation/logic]
3. Component B → [data processing]
4. Output/Result → [final state]
## Key Components
### ComponentName
- **Location**: path/to/component.ext
- **Purpose**: What it does
- **Dependencies**: What it needs
- **Interface**: How others interact with it
## Architecture Insights
- **Pattern**: [pattern name] usage
- **Layer**: [presentation/domain/infrastructure]
- **Separation**: How concerns are separated
- **Integration**: How it connects to other systems
## Dependencies
- **Internal**: List of internal modules/components
- **External**: APIs, libraries, services
- **Data**: Databases, files, caches
## Critical Files for Understanding
1. path/to/most/important/file.ext
2. path/to/second/important/file.ext
[...up to 10 files]
## Observations
- **Strengths**: What's well-implemented
- **Issues**: Problems or technical debt
- **Opportunities**: Areas for improvement
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 · 278 lines · 48 tokens per session scan A 657424cfc020
general-code-explorer is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (363 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,962 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
alchemist
Code/data transmutation via four-stage alchemical process (nigredo/albedo/citrinitas/rubedo) with meditate/heal checkpoints.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
performance-engineer
Use this agent when something is slow or heavy - profiling, Core Web Vitals, bundle size, slow queries, caching, load testing. It measures first and proves improvements with before/after numbers.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Automatically detects Spring Boot or Quarkus and applies framework-specific fixes. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java builds fail.
dynatrace-expert
The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing…
modernize-java
Upgrades Java projects to target versions (e.g., Java 21, Spring Boot 3.2) via incremental planning and execution. Use this agent for all Java upgrade requests.