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 skills add Cavalry-Collective/visual-stack --skill startgit clone --depth 1 https://github.com/Cavalry-Collective/visual-stackWrote 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/cavalry-collective/visual-stack/start)<a href="https://agentmods.dev/skills/cavalry-collective/visual-stack/start"><img src="https://agentmods.dev/badge/skills/cavalry-collective/visual-stack/start/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/cavalry-collective/visual-stack/start"><img src="https://agentmods.dev/badge/skills/cavalry-collective/visual-stack/start.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.00103 | $0.02939 |
| Opus 5.5 | $0.00041 | $0.01176 |
| Sonnet 5.5 | $0.00021 | $0.00588 |
| Haiku 4.5 | $0.00010 | $0.00294 |
Grade C, and why
start scanned grade C 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf <name>/.git && git -C <name> init && git -C <name> add -A How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turns an idea — or an existing repo — into this project. One multi-step form, then whichever of three paths its answers call for.
┌─ skip dev ──► specs/ + design/ only (no clone)
idea ──► setup form ──► choice ──┤
└─ full ─────► clone ──► delete the rest ──► toolchain ──► ready
existing code ──► infer ──► confirm screen ──► recorded (nothing touched)
Every path ends with two files the rest of the chain reads: specs/product.md — what this product
is — and .vstack/pipeline.json — where the pipeline stands.
1 · Pick the mode
Look at the target directory first:
| The directory is | Mode |
|---|---|
| empty, missing, or has no real code | fresh — the form runs before anything exists |
template-derived (stacks/, add-ons/, design/, specs/ all present) |
template — don't clone again; the form reads the real inventory |
| a real codebase that isn't template-derived | existing — infer, confirm, record; never scaffold or delete |
In fresh mode, don't interrogate up front — the form asks the questions. The only thing worth asking before serving it is where the project directory should go if the user hasn't said.
2 · Serve the form
SKILL=<this skill dir>
node "$SKILL/assets/chooser-server.mjs" --repo <project dir> --port 7799
Start it with run_in_background: true, then tell the user to open http://localhost:7799/.
The form is four steps: what are you building → details (kind, name, one-liner) → stack & add-ons, with a pack recommended from the earlier answers — → confirm. On step 3 the user can instead skip development setup entirely; the whole path then produces UI and specs only.
Where the inventory comes from:
- Template mode (repo has
stacks/+add-ons/): scanned from disk — a pack added upstream appears with no change here. - Fresh mode (nothing on disk yet): the server fetches the live
stacks/+add-ons/listing ofvstack-template-basefrom GitHub ("source": "github"); offline or rate-limited it falls back to its built-in catalog snapshot ("source": "snapshot"). Either way, after cloning, reconcile: if the chosen pack or an add-on doesn't exist in the cloned template, stop and re-ask; if the template ships packs the form didn't show, mention them before deleting anything. - Existing mode: no inventory. Infer the facts first — read
package.json/ lockfiles / framework configs / the directory layout /README/ recent git log — write them as a prefill, and serve:
What ships with it
2 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.
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.
- 1mo ago First seen · 216 lines · 103 tokens per session scan C ca729ab94a71
start is a skill published in the GitHub repository Cavalry-Collective/visual-stack (11 stars, last pushed 3d ago), licensed MIT. It adds 103 tokens to every session and 2,939 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
chief-financial-officer
Owns the financial position: planning, budgeting, forecasting, unit economics, cash, and the numbers the business is run and reported on. Use this to build or challenge a budget, model a decision's financial consequence, assess unit economics or runway, evaluate an investment or spend request, set financial controls…
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
support-operations
Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…
ai-ml-governance
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…