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 skills add theshadow27/mcp-cli --skill skillgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/skill)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/skill"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/skill"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/skill.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01578 |
| Opus 5.5 | $0.00000 | $0.00631 |
| Sonnet 5.5 | $0.00000 | $0.00316 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
skill 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 2mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP CLI — Context-Free MCP Tool Access
Use the mcx CLI via Bash instead of native MCP tools. This eliminates 15,000+ tokens of tool definitions per server from every conversation context.
When to Use This
Use mcx CLI when calling MCP server tools (Atlassian, Coralogix, etc.). Use native MCP tools only when mcx CLI is unavailable or for interactive/streaming use cases.
Trigger words: atlassian, confluence, jira, coralogix, mcp server, mcp tool
Quick Reference
# Discovery
mcx ls # list servers + tool counts
mcx ls <server> # list tools for a server
mcx info <server> <tool> # TypeScript-notation schema
mcx grep <pattern> # search tools across all servers
mcx search <query> # search local tools, then registry
# Invocation
mcx call <server> <tool> '<json>' # call a tool, JSON to stdout
mcx call <server> <tool> '<json>' --jq '.field' # client-side jq filter
mcx call <server> <tool> '<json>' --full # bypass output size protection
# Session Management
mcx claude spawn --task "..." # start a Claude Code session
mcx claude ls # list active sessions
mcx claude send <session> <msg> # send follow-up prompt
mcx claude bye <session> # end a session
mcx claude log <session> # view session transcript
mcx claude wait <session> # wait for session to idle
mcx claude wait --any # race: session idle or work item event
mcx claude interrupt <session> # interrupt a running session
mcx mail -H # list inter-session message headers
mcx mail -s "subject" <recipient> # send message (body from stdin)
# Work Item Tracking
mcx track <number> # track an issue or PR by number
mcx track --branch <name> # track a branch (before PR exists)
mcx untrack <number> # stop tracking
mcx tracked # list all tracked work items (table)
mcx tracked --json # machine-readable list
mcx tracked --phase impl # filter by phase
# Virtual Filesystem (clone/push/pull remote content)
mcx vfs clone confluence <space> [dir] # clone a Confluence space as git repo
mcx vfs pull [dir] # pull remote changes
mcx vfs push [dir] # push local changes back to remote
# Server Management
mcx status # daemon health + server status
mcx restart [server] # reconnect server(s)
mcx daemon restart # restart the daemon
mcx daemon shutdown # stop the daemon
mcx logs <server> # view server stderr output
mcx install <server> # install server from registry
mcx upgrade # install latest mcx release binaries
mcx upgrade --check # check for updates
mcx config show # resolved config
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.
- 2mo ago First seen · 146 lines · 0 tokens per session scan A d95352c9c82e
skill is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,578 tokens. 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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…