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/tangonpx skills add egsok/plan-tango --skill tangogit clone --depth 1 https://github.com/egsok/plan-tangoWrote 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/egsok/plan-tango/tango)<a href="https://agentmods.dev/skills/egsok/plan-tango/tango"><img src="https://agentmods.dev/badge/skills/egsok/plan-tango/tango.svg" alt="Measured on agentmods" 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 | $0.00079 | $0.09344 |
| Opus 5 | $0.00039 | $0.04672 |
| Sonnet 5 | $0.00016 | $0.01869 |
| Haiku 4.5 | $0.00008 | $0.00934 |
Grade B, and why
tango 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.
- `--model <m>` (default unset — Codex picks from `~/.codex/config.toml`). How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Works inside plan mode (Read/Edit of plan-file allowed; Bash/Task via permission prompts).
<execution_context>
- Codex CLI:
codex exec --json --sandbox read-only -o <file>fromrun-codex-review.mjs. Required:codexon PATH (codex --version), auth viacodex loginor/codex:setup. - User config (optional):
~/.claude/plan-tango/config.json. CLI overrides. Schema:${CLAUDE_PLUGIN_ROOT}/skills/tango/user-config.example.json. - Helper scripts at
${CLAUDE_PLUGIN_ROOT}/skills/tango/scripts/:plan-paths.mjs(validate/newest/list-recent/resolve-repo/hash),workspace.mjs(ensure/cleanup),snapshot.mjs,lock.mjs(acquire/refresh/release/inspect),apply-fixes.mjs(dry-run classifier → edit_plan + ledger_template + advisory_plan),parse-codex-jsonl.mjs,parse-codex-verdict.mjs.load-config.mjs— merges CLI + config + defaults; emits{merged, sources, warnings}.init.mjs— orchestrates Phase A in one Bash call (validate plan + codex CLI + repo + load-config + lock + state init/resume + workspace ensure). Returns full context bundle for the orchestrator to bind, with internal lock-cleanup on partial failure.prepare-iter.mjs— single deterministic builder for ALL iter{N} artifacts:iter{N}.prompt.md,iter{N}.params.json, empty stubiter{N}.last-message.txt. Settings come inline via--state-settings '<json>'— no per-iteriter{N}.settings.jsonWrite needed (step 13).run-codex-review.mjs—codex execwrapper (called directly via Bash from step 15). Filters cosmetic rollout-recording stderr (seereferences/codex-thread-investigation.md). Retriescodex_empty_outputonce internally before reporting.
- Subagent at
${CLAUDE_PLUGIN_ROOT}/agents/:plan-tango:plan-final-checker(opus, sanity check on converged statuses — Phase D only). - Templates:
references/review-prompt-template.md,references/verdict-contract.md. Schemas (state, params, ledger, verdict): references/schemas.md. </execution_context>
Default thread mode is continue (reuses one Codex thread; injects <reset_iteration> block at iter ≥ 2). Advanced flags — --continue-thread / --fresh-each (override thread mode), --service-tier <fast|flex>, --fast, --codex-profile <name>, extra_codex_config (config field) — are documented in references/advanced-config.md. The loader (load-config.mjs) emits a warnings array the orchestrator surfaces (Phase A step 4). The removed final_check aliases (--no-final-check / --force-final-check, config auto / force) are no longer migrated — the loader hard-errors naming the canonical replacement (--final-check, never / always).
What ships with it
24 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.
- references/advanced-config.md 6.9 KB
- references/codex-thread-investigation.md 5.3 KB
- references/final-check.md 4.7 KB
- references/invariants.md 6.1 KB
- references/report-format.md 4.1 KB
- references/review-prompt-template.md 2.2 KB
- references/schemas.md 12 KB
- references/verdict-contract.md 4.5 KB
- scripts/apply-fixes.mjs 11 KB runs code
- scripts/commit-iter.mjs 9.4 KB runs code
- scripts/doctor.mjs 8.8 KB runs code
- scripts/evaluate-stop.mjs 9.1 KB runs code
- scripts/init.mjs 16 KB runs code
- scripts/load-config.mjs 12 KB runs code
- scripts/lock.mjs 12 KB runs code
- scripts/parse-codex-jsonl.mjs 4.7 KB runs code
- scripts/parse-codex-verdict.mjs 7.2 KB runs code
- scripts/plan-paths.mjs 8.6 KB runs code
- scripts/prepare-iter.mjs 11 KB runs code
- scripts/run-codex-review.mjs 21 KB runs code
- scripts/snapshot.mjs 2.1 KB runs code
- scripts/update-check.mjs 9.9 KB runs code
- scripts/workspace.mjs 5.7 KB runs code
- user-config.example.json 3.6 KB
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 · 276 lines · 79 tokens per session scan B f160893e7ed8
tango is a skill published in the GitHub repository egsok/plan-tango (28 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 9,344 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…