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/cli-setupgit 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.00027 | $0.01049 |
| Opus 5 | $0.00014 | $0.00524 |
| Sonnet 5 | $0.00005 | $0.00210 |
| Haiku 4.5 | $0.00003 | $0.00105 |
Grade B, and why
cli-setup scanned grade B with 1 finding 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 yesterday.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Global hooks: `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Setup Command
Install 1MCP CLI hooks and reference files for Codex or Claude.
Synopsis
npx -y @1mcp/agent cli-setup (--codex | --claude) [options]
Description
The cli-setup command installs lightweight bootstrap files that point Codex or Claude at the 1MCP CLI workflow. It writes:
- A managed
1MCP.mdbootstrap document - Hook configuration so the startup doc is injected on session start
- A startup file reference from
AGENTS.mdorCLAUDE.md
cli-setup does not replace instructions. It makes sure the session is prepared to use instructions, inspect, and run in the right order.
Think of cli-setup as the bridge from an existing agent workflow to 1MCP CLI mode. It teaches the client how to start, but the live discovery and execution flow still happens through instructions, inspect, and run.
Required Client Selection
Choose exactly one target:
--codex- Install setup files for Codex only--claude- Install setup files for Claude only
Passing neither or both returns an error.
Options
--scope <global|repo|all>- Setup scope (default:global)--repo-root <path>- Repository root used for repo-scoped setup
Scope Behavior
global- Writes into the user's home-level Codex or Claude directoriesrepo- Writes repo-local setup files under the selected repository rootall- Writes both global and repo-scoped setup files
Files Written
Codex
- Global managed doc:
~/.codex/1MCP.md - Global hooks:
~/.codex/hooks.json - Global startup reference:
~/.codex/AGENTS.md - Repo managed doc:
<repo>/.codex/1MCP.md - Repo hooks:
<repo>/.codex/hooks.json - Repo startup reference:
<repo>/AGENTS.md
Claude
- Global managed doc:
~/.claude/1MCP.md - Global hooks:
~/.claude/settings.json - Global startup reference:
~/.claude/CLAUDE.md - Repo managed doc:
<repo>/.claude/1MCP.md - Repo hooks:
<repo>/.claude/settings.json - Repo startup reference:
<repo>/CLAUDE.md
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.
- yesterday First seen · 118 lines · 27 tokens per session scan B c59ea6823b9d
cli-setup is a command published in the GitHub repository 1mcp-app/agent (494 stars, last pushed 3d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,049 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
send
Send a WhatsApp message using the wu MCP server.