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/egsok/plan-tango/updatenpx skills add egsok/plan-tango --skill updategit clone --depth 1 https://github.com/egsok/plan-tangoWhat 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.00088 | $0.01581 |
| Opus 5 | $0.00044 | $0.00790 |
| Sonnet 5 | $0.00018 | $0.00316 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
update 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<execution_context>
- Update checker:
${CLAUDE_PLUGIN_ROOT}/skills/tango/scripts/update-check.mjs— handles the 7-day on-disk cache (~/.claude/plan-tango/.update-cache.json),git ls-remote --tagsquery, semver comparison, silent-on-network-failure behaviour. Reused as-is; this skill only adds thegit pullstep on top. - Plugin version source:
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json— read.versionto pass as--current-version. - Marketplace clone: the parent-parent of
${CLAUDE_PLUGIN_ROOT}. The marketplace.jsonsourcefield is./plugins/plan-tango, so the plugin lives at<MARKETPLACE_ROOT>/plugins/plan-tango/. Twocd ..fromCLAUDE_PLUGIN_ROOTreaches the git repo root. - User opt-out:
update_check: falsein~/.claude/plan-tango/config.jsonblocks the SessionStart hook and Phase E notice but does NOT block this skill — running/plan-tango:updateis an explicit user intent, so we always honour it. </execution_context>
Step 1 — Resolve marketplace root + sanity check
MARKETPLACE_DIR="$(cd "${CLAUDE_PLUGIN_ROOT}/../.." && pwd)"
test -d "$MARKETPLACE_DIR/.git" && echo "$MARKETPLACE_DIR" || echo "NOT_GIT"
If output is NOT_GIT → ABORT with:
Cannot self-update: <MARKETPLACE_DIR> is not a git repository. plan-tango
was likely installed via direct git clone or symlink, not through Claude
Code's marketplace. Pull/build the new version manually from
https://github.com/egsok/plan-tango.
Step 2 — Parse flags from $ARGUMENTS
--check— print version status and STOP (no git pull, no AskUserQuestion).--force— skip the clean-working-tree safety check in Step 4. Equivalent to "I know I have local mods, discard them".- No flag — run the full check + confirm + pull flow.
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.
- 2d ago First seen · 138 lines · 88 tokens per session scan A efc83c8044cd
update is a skill published in the GitHub repository egsok/plan-tango (28 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 1,581 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
release-notes
Draft concise release notes.
greptimedb-release
Runbook for publishing a new GreptimeDB version (tag + GitHub release + docs release-note PR) on the upstream GreptimeTeam/greptimedb repo. Use when asked to "release" / "publish" a GreptimeDB version (e.g. v1.1.0, v1.0.3).
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…
store-update
在 CCX Desktop 发布后下载 Store MSIX 并生成发布公告。用户提到 Store 上架、MSIX、从 GitHub Release 下载 store.msix、发布后同步 Windows Store、从 release 填写商店更新内容时必须使用此技能。该技能会下载最新 GitHub Release 的 amd64/arm64 MSIX，校验 sha256，从 Release body 生成 Store listing releaseNotes 预览，并输出手动上传指引。.