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 skills/ankitaa186/host-terminal-mcp/codebase-explorernpx skills add ankitaa186/host-terminal-mcp --skill codebase-explorergit clone --depth 1 https://github.com/ankitaa186/host-terminal-mcpWrote 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/skills/ankitaa186/host-terminal-mcp/codebase-explorer)<a href="https://agentmods.dev/skills/ankitaa186/host-terminal-mcp/codebase-explorer"><img src="https://agentmods.dev/badge/skills/ankitaa186/host-terminal-mcp/codebase-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.1 | $0.00036 | $0.01157 |
| Opus 5 | $0.00018 | $0.00579 |
| Sonnet 5 | $0.00007 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
codebase-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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Explorer
Expert guidance for exploring and understanding codebases.
Exploration Strategy
Phase 1: High-Level Structure
# Get directory tree (limit depth)
tree -L 2 -d
# List top-level contents
ls -la
# Check for documentation
ls README* CONTRIBUTING* docs/ doc/
Phase 2: Project Detection
# Identify project type by manifest files
ls package.json pyproject.toml Cargo.toml go.mod pom.xml build.gradle Gemfile
Phase 3: Deep Dive
# Entry points
cat main.py src/index.js cmd/main.go
# Configuration
cat config/*.yaml .env.example
# Dependencies
cat package.json requirements.txt Cargo.toml
Project Type Detection
| File | Project Type | Next Steps |
|---|---|---|
package.json |
Node.js | Check scripts, dependencies |
pyproject.toml |
Python (modern) | Check [project], [tool.*] |
requirements.txt |
Python (legacy) | Check dependencies |
Cargo.toml |
Rust | Check [package], [dependencies] |
go.mod |
Go | Check module path, dependencies |
pom.xml |
Java (Maven) | Check <dependencies> |
build.gradle |
Java (Gradle) | Check dependencies block |
Gemfile |
Ruby | Check gems |
composer.json |
PHP | Check require |
Makefile |
C/C++/Generic | Check targets |
Finding Key Components
Entry Points
# Common entry point names
find . -name "main.*" -o -name "index.*" -o -name "app.*" | head -20
# Scripts directory
ls bin/ scripts/ cmd/
Configuration
# Config files
find . -name "*.config.*" -o -name "*.yaml" -o -name "*.toml" | grep -v node_modules
Tests
# Test directories and files
find . -type d -name "test*" -o -type d -name "__tests__"
find . -name "*test*.py" -o -name "*.test.js" -o -name "*_test.go"
API/Routes
# Common API patterns
grep -r "app\.\(get\|post\|put\|delete\)" --include="*.js" --include="*.ts"
grep -r "@app\.route\|@router" --include="*.py"
grep -r "func.*Handler\|http\.Handle" --include="*.go"
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 · 178 lines · 36 tokens per session scan A ae86d7bd9194
codebase-explorer is a skill published in the GitHub repository ankitaa186/host-terminal-mcp (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,157 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-09-01.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
Orchestrates Volcengine Cloud Detect (云拨测) false-alarm reduction for failing periodic-task dial points. Use for scheduled task scans, retrying failed nodes, control-testing node health, distinguishing real target outages from broken dial points, and suggesting same-type LastMile/IDC/Private replacement nodes. Runs the…