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/bobbyjohnstx/tinycode/mcp-setupnpx skills add bobbyjohnstx/tinycode --skill mcp-setupgit clone --depth 1 https://github.com/bobbyjohnstx/tinycodeWhat 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.00053 | $0.02190 |
| Opus 5 | $0.00026 | $0.01095 |
| Sonnet 5 | $0.00011 | $0.00438 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
mcp-setup 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Setup
Configure Model Context Protocol (MCP) servers to extend tinycode's capabilities with external tools like web search, file system access, and GitHub integration.
Overview
MCP servers provide additional tools that tinycode agents can use. This skill helps you configure popular MCP servers using the tinycode mcp add command-line interface.
When to Use
Use this skill when:
- The user says "set up MCP", "add an MCP server", "configure Context7/Exa/Filesystem/GitHub", or "extend tinycode with external tools"
- The user wants web search, docs context, file access, or GitHub integration via MCP
- The user wants to add a custom stdio or HTTP MCP server to their tinycode config
When Not to Use
- The user wants to write or code a new MCP server implementation — that is development work, not setup
- The user wants to change tinycode settings, hooks, or permissions — use the
update-configskill - The user needs deep runtime debugging of a failing MCP server beyond the Common Issues list — use
debug - The user already has MCP servers configured and just wants to list or remove them — run
tinycode mcp listortinycode mcp remove <name>directly
Step 1: Choose a Setup Path
Use AskUserQuestion with one question at a time and no more than 3 options per question.
Step 1.1: First menu
Question: "What kind of MCP setup would you like?"
Options:
- Recommended starter setup - Fast path for the most common tinycode MCP additions
- Individual popular server - Pick one server from a short follow-up menu
- Custom server - Add your own stdio or HTTP MCP server
Step 1.2: If the user chooses "Recommended starter setup"
Ask a follow-up AskUserQuestion:
Question: "Which recommended MCP bundle should I configure?"
Options:
- Context7 only (Recommended) - Zero-config docs/context server
- Context7 + Exa - Docs/context plus enhanced web search
- Full recommended bundle - Context7, Exa, Filesystem, and GitHub
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 · 244 lines · 53 tokens per session scan A 10d570a9ca72
mcp-setup is a skill published in the GitHub repository bobbyjohnstx/tinycode (11 stars, last pushed 4d ago), licensed MIT. It adds 53 tokens to every session and 2,190 once invoked, about $0.0003 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-30.
Other skills, from other repositories
system-prompts
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
archon-cli
Drive Archon through its CLI: run AI workflows on a repo, manage those runs (inspect, approve, reject, cancel, resume), set up Archon or change its config, author new workflows, and improve workflow prompts. Use when the user says "use archon", "run archon", "archon workflow", "fix issue #N with archon", "have archon…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
greet
A greeting skill for testing.