Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add YoungjaeDev/my-claude-plugins/plugin install deckWrote 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/youngjaedev/my-claude-plugins/deck-deploy)<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/deck-deploy"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/deck-deploy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/youngjaedev/my-claude-plugins/deck-deploy"><img src="https://agentmods.dev/badge/skills/youngjaedev/my-claude-plugins/deck-deploy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00143 | $0.01068 |
| Opus 5.5 | $0.00057 | $0.00427 |
| Sonnet 5.5 | $0.00029 | $0.00214 |
| Haiku 4.5 | $0.00014 | $0.00107 |
Grade B, and why
deck-deploy scanned grade B 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 today.
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.
found=$(find "$HOME/.claude/plugins/cache" "${CODEX_PLUGIN_CACHE:-$HOME/.codex/plugins/cache}" \ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sI https://<name>.vercel.app | grep -i x-robots-tag # X-Robots-Tag: noindex, nofollow, noarchive How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
deck-deploy
Overview
Publishes the built deck as a static site. The staging folder holds only what the page loads, so the plugin, sections, outline and rules never leave the machine. The Vercel project name comes from the - Vercel 프로젝트: line of deck/outline.md. Search engines are kept out by an X-Robots-Tag: noindex, nofollow, noarchive header and a Disallow: / robots.txt.
When to use
- The user explicitly asks to deploy, and has reviewed the deck locally (dev server or rendered PNGs).
- Not after an edit, a sync, or a passing
deck-checkon your own initiative: deploying is the user's call every time.
Procedure
Interaction gate: Claude uses AskUserQuestion; Codex uses request_user_input when exposed, otherwise asks in plain text and waits. Shell state does not persist between tool calls, so keep the resolver in the same call as each command.
-
Gate. Run
deck-checkfirst. If anything failed, stop and report. Then read the project name fromdeck/outline.mdand ask the user to confirm: "Deploy deck/index.html to Vercel project<name>(https://.vercel.app)?" Proceed only on a yes. A placeholder<project-name>means the outline is unfinished: ask for the name and write it into the outline first. -
Stage only, then inspect (from the repo root).
PLUGIN_ROOT="${PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT:-}}" [ -z "$PLUGIN_ROOT" ] && [ -f plugins/deck/scripts/kit.py ] && PLUGIN_ROOT=plugins/deck if [ -z "$PLUGIN_ROOT" ]; then # find, not a glob: zsh aborts on an unmatched glob and does not split an unquoted list. found=$(find "$HOME/.claude/plugins/cache" "${CODEX_PLUGIN_CACHE:-$HOME/.codex/plugins/cache}" \ -mindepth 3 -maxdepth 3 -type d -path '*/deck/*' 2>/dev/null | awk -F/ '{print $NF "\t" $(0)}') if sort -V </dev/null >/dev/null 2>&1; then PLUGIN_ROOT=$(printf '%s\n' "$found" | sort -V | tail -1 | cut -f2-) else PLUGIN_ROOT=$(printf '%s\n' "$found" | sort -t. -k1,1n -k2,2n -k3,3n | tail -1 | cut -f2-) fi fi [ -f "$PLUGIN_ROOT/scripts/deploy.sh" ] || { echo "deck plugin scripts not found; export PLUGIN_ROOT=<path to plugins/deck>"; exit 1; } DECK_STAGE_ONLY=1 bash "$PLUGIN_ROOT/scripts/deploy.sh" deck
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.
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.
- today Changed 354c8bb6233a
- 13d ago First seen · 62 lines · 143 tokens per session scan B 1f15b2264a34
deck-deploy is a skill published in the GitHub repository YoungjaeDev/my-claude-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 143 tokens to every session and 1,068 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".