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 1mcp-app/agent --skill 1mcp-preparation-setupgit clone --depth 1 https://github.com/1mcp-app/agentWrote 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/1mcp-app/agent/1mcp-preparation-setup)<a href="https://agentmods.dev/skills/1mcp-app/agent/1mcp-preparation-setup"><img src="https://agentmods.dev/badge/skills/1mcp-app/agent/1mcp-preparation-setup/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/1mcp-app/agent/1mcp-preparation-setup"><img src="https://agentmods.dev/badge/skills/1mcp-app/agent/1mcp-preparation-setup.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.00064 | $0.01386 |
| Opus 5.5 | $0.00026 | $0.00554 |
| Sonnet 5.5 | $0.00013 | $0.00277 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
1mcp-preparation-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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up backend preparation
Deliver a configured recipe and evidence for its declared readiness scope. Installing this skill alone changes no backend settings. Use the installed 1MCP CLI and its current help and instructions; recipe support and native backend behavior vary by version.
Establish the target
Identify the runtime (--url or --context, plus configuration location and filters), assigned checkout or selected project-set member, configured server name, native version, current recipe and effective permissions. Normal local calls use the verified startup or worker assignment and omit --project and --project-owner. Keep any explicit target override through discovery, preparation, schema inspection, and invocation; an override does not change the session default.
Follow current bootstrap guidance for ownership. Codex hosts with trustworthy thread lookup resolve their own owner automatically; hosts without that integration use their own bootstrap-provided --project-owner reference. Each worker needs its own explicit assignment and owner. Explicit --url calls remain credentialless unless an owner is explicitly supplied; local credentials do not authorize remote lifecycle controls. Resolve missing assignment before project-specific work.
Reuse current hook-delivered instructions; otherwise fetch scoped 1mcp instructions. Inspect the server and applicable instructions, then tool schemas before invoking tools through 1mcp run. 1mcp project prepare inspect <server> checks readiness even when discovery is empty and does not start preparation. Native CLI help and read-only diagnostics can establish recipe behavior; upstream MCP calls stay routed through 1MCP.
Read only the matching backend reference: CodeGraph, Code Review Graph, or Serena. For other backends, discover their native public setup and readiness interfaces. These examples are conditional techniques, not bundled production recipes.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 51 lines · 64 tokens per session scan A 355c095a37b0
1mcp-preparation-setup is a skill published in the GitHub repository 1mcp-app/agent (524 stars, last pushed today), licensed Apache-2.0. It adds 64 tokens to every session and 1,386 once invoked, about $0.0003 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-10-25.
Other skills, from other repositories
add-permission
Add or reuse a permission end-to-end (backend + frontend) for a new page, tab, endpoint, or protected action in Arthur MCP. Use whenever a feature introduces a new user-facing surface or protected action that needs a permission decision.
session-handoff
Close out a work session on Arthur MCP by updating docs/HANDOFF.md and docs/ROADMAP.md and reporting which validation commands were run. Use at the end of a task, before telling the user work is complete.
release
MUST READ before preparing a release commit or GitHub release -- the blocking GitHub preflight (dev/releasepreflight.py), project.save() versioning, changelog, README, template sync verification, fresh-install smoke, and the post-push GitHub release procedure (references/github-release.md).
specimen-authoring
Workflow and hard-won TD patterns for authoring Embody Specimens (the transparent TDXN gallery networks). Load before building or persisting a Specimen.
multi-instance
Workflow for running multiple TD instances with Envoy, switching between them, and understanding the instance registry.
create-extension
MUST READ before calling createextension. Required parameters, lifecycle methods, and wiring steps.