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/howdeploy/deploychan_mcp/tailored-installnpx skills add howdeploy/deploychan_mcp --skill tailored-installgit clone --depth 1 https://github.com/howdeploy/deploychan_mcpWhat 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.00076 | $0.01850 |
| Opus 5 | $0.00038 | $0.00925 |
| Sonnet 5 | $0.00015 | $0.00370 |
| Haiku 4.5 | $0.00008 | $0.00185 |
Grade B, and why
Tailored Install scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Hooks & permissions:** `~/.claude/settings.json` (user), How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailored Install
The base skill of the deploychan MCP. Whenever you (a connected agent) are about to install a skill, setting/hook, or memory/instruction file for a user, run this discipline first. It is the implicit step 0 of every leveling-up route: "install X" always means "install X tailored to THIS user's machine" — not into a template, not into assumed paths.
This skill is agent-agnostic; the appendices at the end give concrete paths for Claude Code, Hermes and Codex.
Always keep in mind
- Detect before you write. Never assume a path you have not verified.
- Never overwrite blindly. Back up or merge, then confirm.
- Ask when uncertain. A wrong guess pollutes the user's setup.
- Install into the real environment, respecting what already exists.
- Report exactly what changed and where.
Step 1 — Detect the environment (read-only)
Gather facts before touching anything. Read-only only:
- Host agent: Claude Code, Cursor, Cline, Continue, Codex, Hermes, or generic? Look for
tell-tale config dirs/files (e.g. a
.claude/dir, a.cursor/dir, anAGENTS.md). - Which runtime and model you are. This is step 0 of everything: downstream capability choices branch on it. Hermes ships many things out of the box (memory providers, voice); Claude Code / Codex usually vibe-code the equivalent. Pick the wrong branch and you install a Hermes-only command into Claude Code, or hand-build what the host already has.
- OS and home directory.
- Where each surface lives for this agent: skill directory, memory/instruction file(s), hooks/permissions/settings file(s).
- What already exists: installed skills, existing memory file, existing settings — so you can merge instead of clobber.
If a fact cannot be determined read-only, do not guess it — it becomes a question in Step 3.
Step 2 — Resolve target paths
From the detected facts, resolve the real destination for each in-scope surface:
- Skill files — the agent's skill directory (user scope vs project scope).
- Memory / instruction files — the agent's persistent instructions file.
- Hooks / permissions / safe defaults — the agent's settings file.
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 · 181 lines · 76 tokens per session scan B 63dbaa769762
Tailored Install is a skill published in the GitHub repository howdeploy/deploychan_mcp (11 stars, last pushed 4d ago), licensed MIT. It adds 76 tokens to every session and 1,850 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
install-openviking-memory
Install and configure the OpenViking long-term memory plugin for OpenClaw via natural conversation. Once installed, the plugin automatically captures facts from chats and recalls relevant context before each reply (auto-capture + auto-recall, cross-session). Covers prerequisites, install through OpenClaw's plugin…
pipefy-toolkit-setup
Guide a first-time user through Pipefy AI toolkit setup (Cursor Marketplace plugin, hosted MCP, local install.sh, or Claude Code plugin). Use when the user asks to install Pipefy MCP, connect Claude/Cursor to Pipefy, run /pipefy:install, or set up mcp.pipefy.com. Do not use for day-to-day Pipefy workflows after MCP is…
ffmpeg-install
Skill "ffmpeg-install" from chunpu/agent-skills, covering ffmpeg 安装与检查技能, 检查 ffmpeg 是否已安装, 检查 ffmpeg 命令是否存在, macos 安装 and 使用 homebrew 安装（推荐）.
edgeone-clawscan
The first security skill to install after setting up OpenClaw — powered by Tencent Zhuque Lab. Works like an antivirus for your AI environment: audits installed skills, scans skills before installation, and performs a full OpenClaw security health check to prevent data leaks and privacy risks. Backed by Tencent Zhuque…
edgeone skill scanner
Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描…
digital-health-clinical-asr-setup
Stage 1 of Clinical ASR Flywheel. Use when bootstrapping a cycle: NVCF+MW disclosure, NVIDIAAPIKEY check, deps install, TTS+ASR smoke test.