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 commands/1mcp-app/agent/inspectgit clone --depth 1 https://github.com/1mcp-app/agentWhat 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.00028 | $0.01080 |
| Opus 5 | $0.00014 | $0.00540 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
inspect 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 2d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspect Command
Inspect servers or tools from a running 1MCP serve instance.
Synopsis
npx -y @1mcp/agent inspect [target] [options]
Description
The inspect command is the discovery and schema step in the CLI workflow. Use it after instructions and before run.
Depending on the target, inspect can:
- List all exposed servers when no target is provided
- List the exposed tools for a server when the target is
<server> - Show a readable tool schema summary when the target is
<server>/<tool>
When supported, inspect uses the authenticated /api/v1/inspect endpoint first and falls back to the MCP protocol when needed. It reports startup states for configured static servers before the first capability snapshot; use wait when a script must wait for connected with available: true.
This is the command that turns the broad inventory from instructions into a scoped view. First inspect one server, then inspect one tool, and only then move to execution.
Targets
- Omit target - List all servers exposed by the running 1MCP instance
<server>- List tools for one server<server>/<tool>- Inspect a single tool schema
Options
Connection and Filtering
--url, -u <url>- Override auto-detected 1MCP server URL--context <name>- Use a named Runtime Target Context and its saved bearer token, if any--preset, -p <name>- Use a preset when querying the running server--tag-filter, -f <expression>- Apply an advanced tag filter expression--tags <tag>- Apply simple comma-separated tags
Output and Pagination
--format <toon|text|json>- Output format--all- Fetch all tools without pagination for a server target--limit <number>- Page size for server tool listings (default:20)--cursor <cursor>- Cursor returned from a previous paginated response
Related Global Options
--config-dir, -d <path>- Config directory for auth profile lookup and server discovery--cli-session-cache-path <path>- Override the session cache path template used byinspectandrun; supports{pid}and{scope}
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.
- 2d ago First seen · 129 lines · 28 tokens per session scan A a44d3a5eba27
inspect is a command published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,080 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-08-30.
Other commands, from other repositories
go
MCP tool management and workflow proxy.
strict-development-rules
These rules apply strictly to all code modifications and additions within the Gemini CLI project.
release-harn
Run the tag-first Harn release workflow.
harn-release
Run the tag-first Harn release workflow.
web-component
Create a new web component following the established project conventions.
count
Count WhatsApp messages in a chat.