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/timurgaleev/vibestack/skillifynpx skills add timurgaleev/vibestack --skill skillifygit clone --depth 1 https://github.com/timurgaleev/vibestackWhat 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.00035 | $0.01131 |
| Opus 5 | $0.00017 | $0.00566 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade C, and why
skillify 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "skills/<name>" How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to invoke
Use right after a browse/scrape flow worked and the user wants it reusable —
"skillify this", "make this a skill", "save this flow". It writes a new skill in
the local repo so future invocations just run /the-new-name.
/skillify — Codify a flow into a skill
1. Capture the flow
Provenance guard (STOP if it fails). /skillify only codifies a flow that actually ran in this session. If there is no recent, working browse/scrape flow to point at — the user is asking you to invent a skill from scratch — refuse: "skillify codifies a flow that already worked; I don't see one in this session. Run the browse/scrape steps first, confirm they work, then skillify them." Do not fabricate steps.
From the session that just worked, pin down:
- Intent + trigger phrases — what the user will say to invoke it.
- The exact steps — the
$Bverbs /chainthat worked, in order, with the selectors and the URL (or URL pattern / parameter) used. - The output shape — the JSON or summary the flow produced.
If any of these is unclear, ask once with AskUserQuestion. Pick a short
kebab-case name.
2. Locate the repo and write the skill
Find the vibestack repo (the vibe-* binaries are symlinks into it):
REPO="$(cd "$(dirname "$(readlink "${VIBESTACK_HOME:-$HOME/.vibestack}/bin/vibe-config" 2>/dev/null)")/.." 2>/dev/null && pwd || true)"
[ -f "$REPO/install" ] || { echo "REPO_NOT_FOUND"; }
If REPO_NOT_FOUND, ask the user where they cloned vibestack.
Name-collision check (STOP before writing). A new skill must not silently overwrite an existing one:
[ -e "$REPO/skills/<name>" ] && echo "NAME_TAKEN" || echo "NAME_FREE"
If NAME_TAKEN, use AskUserQuestion: "A skill named <name> already exists.
A) Pick a different name, B) Overwrite it (its current SKILL.md is replaced)."
Only proceed to write when the answer is a free name or an explicit overwrite.
Write skills/<name>/SKILL.md with: frontmatter (name, one-sentence
description, allowed-tools, triggers), a ## When to invoke section, the
{{include lib/snippets/browse-setup.md}} directive, the captured $B steps with
their selectors, the extraction/return logic, and a closing
{{include lib/snippets/capture-learnings.md}}. Match the house style of an
existing skill (e.g. skills/scrape/SKILL.md). Keep brand-clean — no external
project names.
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 · 114 lines · 35 tokens per session scan C a51a4e0164a7
skillify is a skill published in the GitHub repository timurgaleev/vibestack (5 stars, last pushed 15d ago), licensed MIT. It adds 35 tokens to every session and 1,131 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
computer-use
Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…
feature-demo-recording
Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…
browser-recording
Record a browser flow as a video/GIF for evidence — animations, transitions, and multi-step interactions that a still screenshot cannot prove. Drives the project's own Playwright through a bundled runner, then converts to mp4 + GIF via ffmpeg. Use when the user asks to record a demo, capture a GIF or video of the UI…
web-browse
Open a REAL external web page so the user can see it in Kiro Crew's Browser panel. PRIMARY path is the browser MCP tool (drives the built-in native panel); playwright-cli is the fallback for remote/plain-browser sessions and for attached logged-in browsers. Use when the user wants to VIEW / verify / "show me" an…
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…
browser-auth
Browse sites that need a logged-in session with playwright-cli, using attach mode, saved storage state, or individual cookies. Use when a page is behind a login wall and a plain open lands on a sign-in screen.