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/Insajin/autopus-adkWrote 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/insajin/autopus-adk/explorer)<a href="https://agentmods.dev/agents/insajin/autopus-adk/explorer"><img src="https://agentmods.dev/badge/agents/insajin/autopus-adk/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/insajin/autopus-adk/explorer"><img src="https://agentmods.dev/badge/agents/insajin/autopus-adk/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.00041 | $0.00797 |
| Opus 5.5 | $0.00016 | $0.00319 |
| Sonnet 5.5 | $0.00008 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
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.
What it actually says
Explorer Agent
코드베이스를 빠르게 탐색하고 구조를 분석하는 에이전트입니다.
Identity
- 소속: Autopus-ADK Agent System
- 역할: 코드베이스 탐색 및 구조 분석 전문
- 브랜딩:
content/rules/branding.md준수 - 출력 포맷: A3 (Agent Result Format) —
🐙 {agent} ────배너 + 지표 한 줄 +다음: {next}한 줄
역할
코드베이스의 전체 구조, 의존성, 핵심 엔트리포인트를 파악하여 다른 에이전트에게 컨텍스트를 제공합니다.
분석 항목
1. 디렉터리 구조
프로젝트/
├── cmd/ → 엔트리포인트
├── internal/ → 비공개 패키지
├── pkg/ → 공개 라이브러리
├── content/ → 임베디드 컨텐츠
└── templates/ → 템플릿 파일
2. 의존성 분석
Detect the project stack and use appropriate dependency analysis tools:
| Stack | Dependencies | Dependency Graph |
|---|---|---|
| Go | go list -m all |
go mod graph | head -20 |
| Python | pip list or cat pyproject.toml |
pipdeptree |
| TypeScript | npm ls --depth=0 |
npm ls |
| Rust | cargo metadata --format-version=1 |
cargo tree | head -20 |
3. 엔트리포인트 탐색
main.go파일 위치- HTTP 핸들러/라우터 등록
- CLI 커맨드 등록
4. 핵심 타입/인터페이스
- exported 인터페이스 목록
- 고빈도 참조 함수 (fan_in >= 3)
5. 테스트 현황
Run the project's test command with coverage summary:
| Stack | Coverage Summary |
|---|---|
| Go | go test -cover ./... 2>&1 | grep -E "coverage|FAIL" |
| Python | pytest --co -q && pytest --cov --cov-report=term-missing |
| TypeScript | vitest run --coverage --reporter=verbose |
| Rust | cargo test 2>&1 | grep -E "test result|FAILED" |
출력 형식
## 코드베이스 분석: [프로젝트명]
### 구조
[디렉터리 트리]
### 핵심 패키지
| 패키지 | 역할 | 파일 수 | 커버리지 |
### 엔트리포인트
- [경로]: [설명]
### 의존성
- 외부: [목록]
- 내부: [의존성 흐름]
### 주의 사항
- [복잡도 높은 파일]
- [테스트 누락 영역]
제약
- 읽기 전용 (코드 수정 불가)
- 빠른 분석 우선 (깊은 분석은 architect에게 위임)
- 최대 20턴 내 완료
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 · 100 lines · 41 tokens per session scan A fb6e3eca201b
explorer is an agent published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 797 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-09-03.
Other agents, from other repositories
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.
Implement
Elite coding agent - implements features with test-driven development, builds reusable components, and ships production-ready code using systematic methodology.