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 skills/edison-watch/custom-mcps/usagenpx skills add Edison-Watch/Custom-MCPs --skill usagegit clone --depth 1 https://github.com/Edison-Watch/Custom-MCPsWhat 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.00492 |
| Opus 5 | $0.00014 | $0.00246 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
usage 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 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.
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.
What it actually says
Usage Guide
This skill teaches you how to use the three interfaces provided by this project.
CLI
# Install
pip install custom-mcps
# Basic usage
edisonmcps --help # see all commands
edisonmcps greet Alice # run a command
edisonmcps config show # view configuration
edisonmcps doctor # check system health
# Global flags (go before the subcommand)
edisonmcps --verbose greet Alice # detailed output
edisonmcps --format json config show # JSON output
edisonmcps --dry-run greet Bob # preview without executing
edisonmcps --version # print version
Server (HTTP API + MCP)
# Start the server: HTTP API and MCP (streamable HTTP) on one port.
edisonmcps-serve
# Default http://localhost:8080. See /docs for OpenAPI, /mcp for MCP.
MCP
The MCP server exposes the same services as CLI tools via the Model Context Protocol.
Primary transport: streamable HTTP at /mcp (started by edisonmcps-serve).
Stdio is supported via edisonmcps-mcp for local Claude Desktop / dev only.
# Legacy stdio transport
edisonmcps-mcp
# Debug with the MCP inspector (stdio)
mcp dev mcp_server/server.py
Connecting MCP to your editor
Remote (preferred - works on Claude Desktop 0.7+, Cursor, etc.):
{
"mcpServers": {
"edisonmcps": {
"url": "https://YOUR-DEPLOYMENT/mcp",
"headers": { "X-API-KEY": "sk_..." }
}
}
}
Local stdio (legacy):
{
"mcpServers": {
"edisonmcps": {
"command": "edisonmcps-mcp"
}
}
}
Updating
edisonmcps update # check for updates and upgrade
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 · 84 lines · 27 tokens per session scan A 4b9ebd75a085
usage is a skill published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 492 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.