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 instructions/inboxapi/cli/gemini-mdgit clone --depth 1 https://github.com/inboxapi/cliWhat 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.01107 | $0.01107 |
| Opus 5 | $0.00553 | $0.00553 |
| Sonnet 5 | $0.00221 | $0.00221 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
cli GEMINI.md scanned grade A 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Pass arguments as arrays to `execFileSync` — never use string interpolation with `execSync` (shell injection risk) How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
InboxAPI CLI — Gemini Agent Context
Overview
Rust STDIO proxy that bridges JSON-RPC (MCP protocol) over STDIO to the remote InboxAPI MCP service over Streamable HTTP/SSE. Distributed as @inboxapi/cli on npm with platform-specific binary packages.
Technology Stack
- Language: Rust (Tokio async runtime, reqwest HTTP client, eventsource-client SSE)
- Protocol: JSON-RPC over STDIO (MCP standard)
- Transport: HTTP POST + SSE to remote endpoint
- Distribution: npm with platform-specific optional dependencies
- CI: GitHub Actions (5-platform cross-build, GitHub Releases, npm publish)
Commands
cargo build # Build binary
cargo test # Run tests
cargo fmt # Format code
cargo run -- proxy # Start STDIO proxy (default)
cargo run -- login # Authenticate and store credentials
cargo run -- whoami # Show current account
# CLI subcommands
cargo run -- send-email --to [email protected] --subject "Hi" --body "Hello"
cargo run -- send-email --to [email protected] --subject "Newsletter" --body-file ./body.txt --html-body-file ./newsletter.html
cargo run -- get-emails --limit 5
cargo run -- get-email "<message-id>"
cargo run -- search-emails --subject "keyword"
cargo run -- get-attachment <id> --output ./file.pdf
cargo run -- send-reply --message-id "<id>" --body "Reply"
cargo run -- send-reply --message-id "<id>" --body-file ./reply.txt --html-body-file ./reply.html
cargo run -- forward-email --message-id "<id>" --to [email protected]
cargo run -- help
Prefer --body-file and --html-body-file for complex HTML, templates, or large generated content. File-backed bodies are validated as UTF-8 text, normalized to \n, and capped at 20 MiB.
Development Workflow
- Single Rust source file (
src/main.rs) containing all proxy, auth, and CLI logic index.jsis the npm entry point — resolves platform binary or falls back tocargo run- Tags (
v*.*.*) trigger CI builds and npm publishing
Key Files
src/main.rs— Proxy loop, token injection, login flow, hashcash proof-of-workindex.js— npm binary resolver (platform package → local build → cargo run)package.json— Root npm package withoptionalDependenciesfor 5 platformsnpm/cli-*/package.json— Platform-specific package manifests (os/cpu fields).github/workflows/release.yml— Cross-build, GitHub Release, npm publish pipelineCargo.toml— Rust project configuration and dependencies
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 · 93 lines · 1,107 tokens per session scan A f532fa6721f5
cli GEMINI.md is an instructions file published in the GitHub repository inboxapi/cli (12 stars, last pushed 2mo ago), licensed MIT. It adds 1,107 tokens to every session, about $0.0055 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
postmark-mcp CLAUDE.md
Instructions for ActiveCampaign/postmark-mcp, covering claude.md, project overview, commands, architecture and mcp tools registered.
email-templates CLAUDE.md
Instructions for ColorlibHQ/email-templates, covering claude.md, repository purpose, layout, commands and editing or adding a template.
mcp-dotnet-samples AGENTS.md
Instructions for microsoft/mcp-dotnet-samples, covering agents.md - mcp .net samples, project overview, project structure and architecture, repository organization and sample components.
Embody AGENTS.md
Instructions for dylanroscover/Embody, covering embody + envoy - ai instructions, critical rules, td python rules, network layout rules and mcp server safety rules.
cli AGENTS.md
Instructions for nylas/cli, covering ai coding agent guidelines, quick reference: shared helpers, quick reference: adding a new feature and quick reference: credential storage.
better-email-mcp CLAUDE.md
Instructions for n24q02m/better-email-mcp, covering claude.md - better-email-mcp, commands, setup, lint & type check and fix.