techpack-creator

A packaging workflow that turns an existing Claude Code setup into an MCS tech pack, a shareable bundle of coding-agent configuration.

In plain words
What is it for?
It is for scanning a configured repository or exporting its live setup, then creating a techpack.yaml file and supporting files for sharing through the mcs command-line tool.
Why use it?
It saves developers from manually documenting and assembling skills, hooks, commands, agents, settings, and connected services for distribution.

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/mcs-cli/mcs/techpack-creator
Any agent
npx skills add mcs-cli/mcs --skill techpack-creator
Clone the repo
git clone --depth 1 https://github.com/mcs-cli/mcs

Made for: Claude Code, Codex.

Per session 190 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,919 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00190 $0.03919
Opus 5 $0.00095 $0.01959
Sonnet 5 $0.00038 $0.00784
Haiku 4.5 $0.00019 $0.00392

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

Security

Grade A, and why

techpack-creator scanned grade A with 1 finding 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.

Makes network callslowCapability

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

fixCommand: '/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"'
skills/techpack-creator/SKILL.md · 370 lines

How it starts

The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.

TechPack Creator

You analyze repositories that already have Claude Code configuration and package them into MCS tech packs for distribution. A tech pack is a Git-distributable bundle of Claude Code configuration — MCP servers, hooks, skills, commands, agents, templates, and settings — defined in a single techpack.yaml manifest that the mcs CLI syncs and maintains.

Two approaches — choose based on what's available:

  1. mcs export first (recommended when MCS is installed): Run mcs export ./pack-output to capture the live Claude Code configuration as a starting point. Then review and improve the generated techpack.yaml — add dependencies between components, add prompts for env vars, add doctor checks, and wire up templates. This is the fastest path when the user already has a working Claude Code session.

  2. Direct scan (when no live config or MCS is not installed): Analyze the repo's files and directory structure directly — read hook scripts, skill directories, command files, settings JSON, CLAUDE.md content, and project manifests to understand what the repo provides. Generate the techpack.yaml and supporting files from scratch.

Both approaches produce the same output: a complete pack directory ready for mcs pack add.

Bundled references (read on demand, not upfront):

  • references/techpack-schema.md — Complete field-by-field schema for techpack.yaml
  • references/stack-detection.md — File-to-stack mapping and component recommendations
  • references/examples/ — Realistic example techpacks (swift-ios.yaml, node-web.yaml, python-ml.yaml)

Remote documentation — use these for the latest info and link them in generated READMEs:

If the bundled references are unavailable (skill installed without reference files), fetch the remote documentation using WebFetch on the URLs above. The remote docs are the canonical source of truth.

Read the full file on GitHub · 370 lines

Files

What ships with it

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

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 · 370 lines · 190 tokens per session scan A aab54eb0c978

Subscribe to this mod's changes

techpack-creator is a skill published in the GitHub repository mcs-cli/mcs (93 stars, last pushed 1mo ago), licensed MIT. It adds 190 tokens to every session and 3,919 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

Evaluation

Frames model, prompt, and system evaluation as a reproducible experiment with baselines, datasets, and explicit metrics.

agentic-in/elephant-agent · 25 tokens

a2ui-renderer

Render A2UI (Agent-to-UI declarative surfaces) in CopilotKit v2. Enable the runtime via CopilotRuntime({ a2ui: {...} }), then enable the provider via . Auto-activates via /info — do NOT manually pass renderActivityMessages. createA2UIMessageRenderer ships from @copilotkit/react-core/v2; low-level primitives…

CopilotKit/CopilotKit · 175 tokens

copilotkit-develop

Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.

CopilotKit/CopilotKit · 46 tokens

copilotkit-upgrade

Use when migrating a CopilotKit v1 application to v2 -- updating package imports, replacing deprecated hooks and components, switching from GraphQL runtime to AG-UI protocol runtime, and resolving breaking API changes.

CopilotKit/CopilotKit · 48 tokens

artifact-deploy

One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".

kirodotdev/KiroCrew · 74 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens