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 timurgaleev/vibestack --skill claudegit clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/claude)<a href="https://agentmods.dev/skills/timurgaleev/vibestack/claude"><img src="https://agentmods.dev/badge/skills/timurgaleev/vibestack/claude.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.1 | $0.00049 | $0.02583 |
| Opus 5 | $0.00024 | $0.01291 |
| Sonnet 5 | $0.00010 | $0.00517 |
| Haiku 4.5 | $0.00005 | $0.00258 |
Grade A, and why
claude 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 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.
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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to invoke
Use when asked for "claude review", "claude challenge", "ask claude", "second opinion from claude", or "outside voice".
Preamble
eval "$(~/.vibestack/bin/vibe-slug 2>/dev/null)" 2>/dev/null || SLUG="unknown"
_LEARN_FILE="${VIBESTACK_HOME:-$HOME/.vibestack}/projects/${SLUG:-unknown}/learnings.jsonl"
if [ -f "$_LEARN_FILE" ]; then
_LEARN_COUNT=$(wc -l < "$_LEARN_FILE" 2>/dev/null | tr -d ' ')
echo "LEARNINGS: $_LEARN_COUNT entries loaded"
if [ "$_LEARN_COUNT" -gt 5 ] 2>/dev/null; then
~/.vibestack/bin/vibe-learnings-search --limit 5 2>/dev/null || true
fi
else
echo "LEARNINGS: none yet"
fi
{{include lib/snippets/session-host.md}}
{{include lib/snippets/decision-brief.md}}
{{include lib/snippets/working-protocols.md}}
{{include lib/snippets/state-protocols.md}}
Base Branch
BASE_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main")
/claude - Claude Outside Voice
This skill wraps claude -p to get an independent Claude Code second opinion
without allowing nested Claude to modify files.
The generated external invocation name is vibe-claude.
Step 0: Check Claude CLI
CLAUDE_BIN=$(command -v claude 2>/dev/null || echo "")
[ -z "$CLAUDE_BIN" ] && echo "NOT_FOUND" || echo "FOUND: $CLAUDE_BIN"
If NOT_FOUND, stop and tell the user:
"Claude CLI not found. Install Claude Code, then re-run this skill."
Do not infer authentication state from credential files or environment
variables, and do not gate on them. Claude Code may hold its credentials in an
OS keychain that is invisible from inside the host agent's sandbox, so a
file-existence check reports a blocker on a perfectly authenticated machine and
the skill refuses to run at all. Only report an authentication problem when the
actual claude -p invocation below returns an auth, login, or unauthorized
error.
Resolve the binary and invoke it in the same host execution context — do not
resolve it inside a sandbox and then run a different claude from another PATH.
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 Changed · -2 lines 2a69c962a9cd
- 6d ago First seen · 365 lines · 49 tokens per session scan A 66609cd1bff5
claude is a skill published in the GitHub repository timurgaleev/vibestack (6 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 2,583 once invoked, about $0.0002 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-31.
Other skills, from other repositories
blind-spot-pass
Run a pre-build blind spot pass before the agent builds anything. Treat the user's prompt as the map and the real project as the territory: classify gaps across known knowns, known unknowns, unknown knowns, and unknown unknowns (with deps, edge cases, and blast radius under unknown unknowns); ask 5 to 10 high-leverage…
merge-open-prs
Review, verify (Docker by default), and auto-merge open PRs when CI, reviews, and local verification pass. Batch up to 10 PRs per run. Use when the user wants to merge all open PRs, clear the PR queue, or run /merge-open-prs.
code-review
Structured code review practices for receiving feedback, requesting reviews, and verification gates. Use when reviewing or receiving review feedback on code changes.
thermo-nuclear-code-quality-review
Extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use only when explicitly asked for a thermo-nuclear or thermonuclear code quality review, a deep code quality audit, or an especially harsh maintainability review.
code-review
Thorough PR code review before approval.
address-github-pr-comments
Address review comments on the current GitHub PR.