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/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/commands/ankitaa186/host-terminal-mcp/explore)<a href="https://agentmods.dev/commands/ankitaa186/host-terminal-mcp/explore"><img src="https://agentmods.dev/badge/commands/ankitaa186/host-terminal-mcp/explore.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.00010 | $0.00624 |
| Opus 5 | $0.00005 | $0.00312 |
| Sonnet 5 | $0.00002 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
explore 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Exploration
Explore and understand codebases, directory structures, and file contents.
Workflow
- Identify target - directory path or search criteria
- Gather structure - list files, directories, key patterns
- Analyze contents - read important files (README, configs, entry points)
- Summarize findings - present organized overview
Usage
/explore <path>
/explore <natural language query>
Exploration Commands Used
This command orchestrates multiple ~~terminal operations:
| Operation | Command |
|---|---|
| Directory listing | ls -la <path> |
| Tree structure | tree -L 3 <path> |
| Find files | find <path> -name "<pattern>" |
| File contents | cat <file> |
| Search content | grep -r "<pattern>" <path> |
| File info | file <path>, wc -l <file> |
Examples
Explore a project
/explore ~/projects/myapp
Returns: directory structure, key files, project type detection
Find specific files
/explore find all test files
Executes: find . -name "*test*.py" -o -name "*_test.go" -o -name "*.test.js"
Understand project structure
/explore what's the architecture of this codebase
Analyzes: README, package.json/pyproject.toml, src/ structure, entry points
Search for patterns
/explore where is authentication handled
Searches: grep -r "auth\|login\|session" --include="*.py"
Auto-Detection
The explore command automatically detects:
- Project type: Node.js, Python, Go, Rust, Java, etc.
- Build system: npm, pip, cargo, maven, gradle
- Framework: React, Django, FastAPI, Express, etc.
- Key files: Entry points, configs, tests, docs
Output Format
📁 Project: myapp
📋 Type: Python (FastAPI)
📦 Dependencies: requirements.txt (23 packages)
Structure:
├── src/
│ ├── main.py (entry point)
│ ├── api/
│ ├── models/
│ └── utils/
├── tests/
├── docs/
└── config/
Key Files:
- README.md: Project documentation
- pyproject.toml: Build configuration
- src/main.py: FastAPI application entry
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.
- 7d ago First seen · 99 lines · 10 tokens per session scan A 62e33b4b48c1
explore is a command published in the GitHub repository ankitaa186/host-terminal-mcp (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 10 tokens to every session and 624 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.