setup

A setup check for dependencies used by FCP tools, including Node.js, uv, and fcp-terraform. Dependencies are external programs that other tools need in order to run.

In plain words
What is it for?
Use it to check versions, identify missing dependencies, install selected items, and verify that the associated servers start correctly.
Why use it?
It shows which required programs are missing before you use the related tools and can guide their installation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/os-tack/fcp/setup
Any agent
npx skills add os-tack/fcp --skill setup
Clone the repo
git clone --depth 1 https://github.com/os-tack/fcp

Made for: Claude Code, Codex.

Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 401 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00401
Opus 5 $0.00010 $0.00200
Sonnet 5 $0.00004 $0.00080
Haiku 4.5 $0.00002 $0.00040

Measured 2d ago against content hash bf676258288f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

setup scanned grade C with 2 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 2d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

- **uv**: `curl -LsSf https://astral.sh/uv/install.sh | sh`

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- **uv**: `curl -LsSf https://astral.sh/uv/install.sh | sh`
skills/setup/SKILL.md · 39 lines

What it actually says

FCP Setup

Check for required FCP dependencies and install any that are missing.

Steps

  1. Check dependencies — run each check and collect results:

    Dependency Check command Needed for
    node node --version drawio
    uv uv --version midi, sheets, slides
    fcp-terraform fcp-terraform --version terraform
  2. Report status — show a table of what's installed and what's missing. If everything is present, say so and stop.

  3. Install missing dependencies — for each missing dependency, offer to install it:

    • uv: curl -LsSf https://astral.sh/uv/install.sh | sh
    • fcp-terraform: curl -LsSf https://github.com/os-tack/fcp-terraform/releases/latest/download/install.sh | sh
    • node: Direct user to https://nodejs.org/ (cannot auto-install)

    Ask the user which missing dependencies they want to install. Install the selected ones.

  4. Verify MCP servers — for each newly installed dependency, verify the MCP server can start:

    • drawio: npx -y @ostk-ai/fcp-drawio --help (or similar smoke test)
    • midi: uvx --refresh-package fcp-midi --python 3.13 fcp-midi --help
    • sheets: uvx --refresh-package fcp-sheets --python 3.13 fcp-sheets --help
    • terraform: fcp-terraform --help
  5. Summary — report final status of all dependencies.

Changes

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.

  1. 2d ago First seen · 39 lines · 19 tokens per session scan C bf676258288f

Subscribe to this mod's changes

setup is a skill published in the GitHub repository os-tack/fcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 401 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

design-mcp-server

Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.

cyanheads/obsidian-mcp-server · 62 tokens

api-canvas

DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…

cyanheads/obsidian-mcp-server · 85 tokens

field-test

Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…

cyanheads/obsidian-mcp-server · 76 tokens

api-config

Reference for core and server configuration in @cyanheads/mcp-ts-core. Covers env var tables with defaults, priority order, server-specific Zod schema pattern, and Workers lazy-parsing requirement.

cyanheads/obsidian-mcp-server · 43 tokens

api-telemetry

Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…

cyanheads/obsidian-mcp-server · 85 tokens

maintenance

Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…

cyanheads/obsidian-mcp-server · 75 tokens