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.
git clone --depth 1 https://github.com/clarsbyte/washedmcpWrote 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/commands/clarsbyte/washedmcp/install-mcp)<a href="https://agentmods.dev/commands/clarsbyte/washedmcp/install-mcp"><img src="https://agentmods.dev/badge/commands/clarsbyte/washedmcp/install-mcp/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/commands/clarsbyte/washedmcp/install-mcp"><img src="https://agentmods.dev/badge/commands/clarsbyte/washedmcp/install-mcp.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.00009 | $0.00291 |
| Opus 5.5 | $0.00004 | $0.00116 |
| Sonnet 5.5 | $0.00002 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
install-mcp 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 1mo 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.
What it actually says
Install MCP Server
You are helping the user install an MCP server. The user wants to install: $ARGUMENTS
Steps
-
Search for the server: Use
mcp__washedmcp__searchSmitheryto find the server matching "$ARGUMENTS" -
Detect required credentials: Use
mcp__washedmcp__detectCapabilitieswith the server name to identify what environment variables/API keys are needed -
Prompt for credentials: If any environment variables are required, use AskUserQuestion to ask the user for ALL required credentials at once. Include:
- The variable name (e.g., GITHUB_PERSONAL_ACCESS_TOKEN)
- What it's for
- Where to get it (provide helpful URLs like https://github.com/settings/tokens for GitHub)
-
Install the server: Call
mcp__washedmcp__installFromSmitherywith:- serverName: the qualified server name
- envVars: JSON string of the credentials provided by user
-
Confirm installation: Tell the user the installation was successful and list the tools now available.
Important
- Always detect and prompt for credentials BEFORE attempting installation
- Provide helpful links for where to obtain API keys
- If installation fails, explain why and offer to retry
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.
- 1mo ago First seen · 30 lines · 9 tokens per session scan A 408ae2793b19
install-mcp is a command published in the GitHub repository clarsbyte/washedmcp (4 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 291 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.