techniques

A reference catalogue of reusable patterns for MCP servers built with the @cyanheads/mcp-ts-core framework. MCP is a standard way for AI assistants to call tools and retrieve data.

In plain words
What is it for?
Use it when shaping tool payloads, creating outlines for large documents, or designing how clients retrieve data in stages.
Why use it?
It helps developers handle oversized, awkward, or costly tool responses using documented approaches instead of designing each solution from scratch.

Skill for Claude CodeCodex

Part of the workflows-mcp-server plugin — 34 skills, 1 MCP server shipped together

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/cyanheads/workflows-mcp-server/techniques
Any agent
npx skills add cyanheads/workflows-mcp-server --skill techniques
Clone the repo
git clone --depth 1 https://github.com/cyanheads/workflows-mcp-server

Made for: Claude Code, Codex.

Or install workflows-mcp-server, the plugin that ships this one along with the rest of its 34 skills, 1 MCP server.

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 487 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00079 $0.00487
Opus 5 $0.00039 $0.00244
Sonnet 5 $0.00016 $0.00097
Haiku 4.5 $0.00008 $0.00049

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

Security

Grade A, and why

techniques 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.

Origin

This is a copy

100% identical to techniques — 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.

skills/techniques/SKILL.md · 33 lines

What it actually says

Overview

A directory of cross-cutting techniques for shaping what a handler returns and how a client retrieves it — patterns that don't belong to a single API surface. Each entry is a self-contained reference under references/: the problem it solves, when to reach for it (and when not to), and how to apply it with current framework primitives.

These are patterns, not new primitives — they compose tool(), output/format() shaping, ctx.state, and the existing helpers. Where a technique has (or will have) a dedicated helper, its reference says so and links the tracking issue.

Techniques

Technique Path Use when
Outline-on-overflow references/outline-on-overflow.md A single tool call returns one document-shaped payload too big to inline (e.g. a ~130KB record), and you want an honest section outline + a re-call contract instead of truncating.

Adding a technique

One file under references/, one row above. A technique earns a place here when it's a reusable response/retrieval pattern that (a) spans more than one tool or server and (b) isn't already covered by an api-* reference. Keep the reference concise: problem → when-to-use → how-to with current primitives → helper status. Bump metadata.version on any change (skill-versioning policy).

  • design-mcp-server — choosing the tool surface and output shapes up front.
  • add-tool — the tool() builder, format()structuredContent parity, matching response density to context budget.
  • api-canvasspillover(), the row-collection sibling of outline-on-overflow.
Files

What ships with it

1 file 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.

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. 3d ago First seen · 33 lines · 79 tokens per session scan A 8f01d620e53c

Subscribe to this mod's changes

techniques is a skill published in the GitHub repository cyanheads/workflows-mcp-server (31 stars, last pushed 12d ago), licensed Apache-2.0. It adds 79 tokens to every session and 487 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to techniques, differing in 0 lines, and is treated as a copy.