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/cyanheads/workflows-mcp-server/api-confignpx skills add cyanheads/workflows-mcp-server --skill api-configgit clone --depth 1 https://github.com/cyanheads/workflows-mcp-serverWrote 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/cyanheads/workflows-mcp-server/api-config)<a href="https://agentmods.dev/skills/cyanheads/workflows-mcp-server/api-config"><img src="https://agentmods.dev/badge/skills/cyanheads/workflows-mcp-server/api-config.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.05235 |
| Opus 5 | $0.00022 | $0.02618 |
| Sonnet 5 | $0.00009 | $0.01047 |
| Haiku 4.5 | $0.00004 | $0.00524 |
Grade A, and why
api-config 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 3d 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.
This is a copy
100% identical to api-config — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Configuration has two layers: core config (managed by the framework, env-driven) and server config (your own Zod schema for domain-specific env vars). Never merge them.
Import: AppConfig, config, parseConfig, resetConfig, ConfigSchema from @cyanheads/mcp-ts-core/config.
Core config
Managed by @cyanheads/mcp-ts-core. Validated via Zod from environment variables. Uses a lazy proxy — parsing is deferred until the first property read.
Priority (highest to lowest):
name/version/title/websiteUrl/description/iconsoptions passed tocreateApp()orcreateWorkerHandler()- Environment variables
package.jsonfields
Identity
| Env Var | AppConfig field |
Default | Notes |
|---|---|---|---|
MCP_SERVER_NAME |
mcpServerName |
package.json name |
Overrides package name |
MCP_SERVER_VERSION |
mcpServerVersion |
package.json version |
Overrides package version |
MCP_SERVER_DESCRIPTION |
mcpServerDescription |
package.json description |
Optional; createApp({ description }) wins when set |
PACKAGE_NAME |
pkg.name |
package.json name |
Rarely needed |
PACKAGE_VERSION |
pkg.version |
package.json version |
Rarely needed |
SDK identity fields (API-only, no env var equivalent — passed to createApp() / createWorkerHandler(), forwarded to initialize and /.well-known/mcp.json):
| Option | Type | Notes |
|---|---|---|
title |
string? |
Human-readable display name shown in client listings |
websiteUrl |
string? |
Canonical homepage / repository URL |
description |
string? |
One-line description; wins over MCP_SERVER_DESCRIPTION when set |
icons |
Implementation['icons']? |
Array of icon objects: { src, mimeType?, sizes?: string[], theme?: 'light'|'dark' } |
cacheHints |
CacheHints? |
Cache hints for the 2026-07-28 cacheable results, keyed by operation — see below |
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.
- 3d ago First seen · 289 lines · 43 tokens per session scan A 9b2ee869e324
api-config is a skill published in the GitHub repository cyanheads/workflows-mcp-server (31 stars, last pushed 12d ago), licensed Apache-2.0. It adds 43 tokens to every session and 5,235 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to api-config, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
test-workflow
Universal n8n workflow testing via webhook or sub-workflow pattern.
dagster-docs
Expert guidance for writing documentation for the Dagster docs website. ALWAYS use before creating or updating documentation in the docs directory.
sofagent-fde
前线部署与知识工程专家。梳理企业业务流、识别 AI 节点、构建 ontology 本体数据、交付离场。 部署完成后转为持续优化模式（sustain），自动读 audit 报告趋势生成优化报告。 不写应用代码——把企业业务规则、组织架构、系统边界转译成 sofagent 的数据层和约束层。.
sofagent-audit
收到用户任务后，不要自己执行——用 Bash tool 把任务交给 DeepAgents 编排引擎：.
sop-mcp-usage
How to use the SOP-MCP server to execute, create, and improve Standard Operating Procedures.
frontend-ui-engineering
Build user-facing UI with responsive behavior, accessibility, runtime validation, and design-system consistency.