A command-line tool for asking AI models questions and running repository-focused tasks such as planning or documentation. It can use models from several providers, but direct questions do not automatically include your codebase context.

Use it to query a chosen AI model, plan work, inspect a repository, or generate documentation from project context.

It gives developers one terminal interface for different AI providers while making clear that useful repository answers need the relevant code or context supplied.

vibe-tools — Cursor rule for Cursor by lacymorrow/paperclip-hub

Install

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.

Clone the repo

git clone --depth 1 https://github.com/lacymorrow/paperclip-hub

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/vibe-tools/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/vibe-tools)

Your own site

<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/vibe-tools"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/vibe-tools/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/vibe-tools"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/vibe-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 3,599 This file is loaded in full into every session.

When invoked 3,599 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 86% copy Near-identical to another mod in the catalogue.

Token cost

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.03599	$0.03599
Opus 5.5	$0.01440	$0.01440
Sonnet 5.5	$0.00720	$0.00720
Haiku 4.5	$0.00360	$0.00360

Measured yesterday against content hash 03600ecf34bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibe-tools 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 yesterday.

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.

Origin

This is a copy

86% identical to vibe-tools — 62 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/rules/vibe-tools.mdc · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

vibe-tools is a CLI tool that allows you to interact with AI models and other tools. vibe-tools is installed on this machine and it is available to you to execute. You're encouraged to use it.

Direct Model Queries: vibe-tools ask "<your question>" --provider <provider> --model <model> - Ask any model from any provider a direct question (e.g., vibe-tools ask "What is the capital of France?" --provider openai --model o3-mini). Note that this command is generally less useful than other commands like repo or plan because it does not include any context from your codebase or repository. Note: in general you should not use the ask command because it does not include any context - other commands like doc, repo, or plan are usually better. If you are using it, make sure to include in your question all the information and context that the model might need to answer usefully.

Ask Command Options: --provider=: AI provider to use (openai, anthropic, perplexity, gemini, modelbox, or openrouter) --model=: Model to use (required for the ask command) --reasoning-effort=<low|medium|high>: Control the depth of reasoning for supported models (OpenAI o1/o3-mini models and Claude 3.7 Sonnet). Higher values produce more thorough responses for complex questions.

Implementation Planning: vibe-tools plan "<query>" - Generate a focused implementation plan using AI (e.g., vibe-tools plan "Add user authentication to the login page") The plan command uses multiple AI models to:

Identify relevant files in your codebase (using Gemini by default)
Extract content from those files
Generate a detailed implementation plan (using OpenAI o3-mini by default)

Plan Command Options: --fileProvider=: Provider for file identification (gemini, openai, anthropic, perplexity, modelbox, or openrouter) --thinkingProvider=: Provider for plan generation (gemini, openai, anthropic, perplexity, modelbox, or openrouter) --fileModel=: Model to use for file identification --thinkingModel=: Model to use for plan generation

Web Search: vibe-tools web "<your question>" - Get answers from the web using a provider that supports web search (e.g., Perplexity models and Gemini Models either directly or from OpenRouter or ModelBox) (e.g., vibe-tools web "latest shadcn/ui installation instructions") Note: web is a smart autonomous agent with access to the internet and an extensive up to date knowledge base. Web is NOT a web search engine. Always ask the agent for what you want using a proper sentence, do not just send it a list of keywords. In your question to web include the context and the goal that you're trying to acheive so that it can help you most effectively. when using web for complex queries suggest writing the output to a file somewhere like local-research/.md.

Web Command Options: --provider=: AI provider to use (perplexity, gemini, modelbox, or openrouter)

Repository Context: vibe-tools repo "<your question>" [--subdir=<path>] [--from-github=<username/repo>] - Get context-aware answers about this repository using Google Gemini (e.g., vibe-tools repo "explain authentication flow"). Use the optional --subdir parameter to analyze a specific subdirectory instead of the entire repository (e.g., vibe-tools repo "explain the code structure" --subdir=src/components). Use the optional --from-github parameter to analyze a remote GitHub repository without cloning it locally (e.g., vibe-tools repo "explain the authentication system" --from-github=username/repo-name).

Documentation Generation: vibe-tools doc [options] - Generate comprehensive documentation for this repository (e.g., vibe-tools doc --output docs.md) when using doc for remote repos suggest writing the output to a file somewhere like local-docs/.md.

YouTube Video Analysis: vibe-tools youtube "<youtube-url>" [question] [--type=<summary|transcript|plan|review|custom>] - Analyze YouTube videos and generate detailed reports (e.g., vibe-tools youtube "https://youtu.be/43c-Sm5GMbc" --type=summary) Note: The YouTube command requires a GEMINI_API_KEY to be set in your environment or .vibe-tools.env file as the GEMINI API is the only interface that supports YouTube analysis.

Read the full file on GitHub · 177 lines

Changes

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.

yesterday First seen · 177 lines · 3,599 tokens per session scan A 03600ecf34bd

Subscribe to this mod's changes

vibe-tools is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It adds 3,599 tokens to every session, about $0.0144 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to vibe-tools, differing in 62 lines, and is treated as a copy.

Building agents ai-agents drizzle-orm nextjs paperclip payload-cms plugin-registry

vibe-tools next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vibe-toolslacymorrow/paperclip-hub	Cursor rule	15	yesterday	MIT	A	3,599	Cursor
always-push-pritsmemeworks/adhx	Cursor rule	19	5d ago	MIT	A	279	Cursor
codex-premium-website-skillsTheGoat395/Codex-Skills	Cursor rule	137	20d ago	MIT	A	0	Cursor
context-managementvibestackdev/vibe-stack	Cursor rule	8	yesterday	MIT	A	0	Cursor
project-contextvibestackdev/vibe-stack	Cursor rule	8	yesterday	MIT	A	508	Cursor
typescript-coding-styleWebDevPeterGriffin/The-VibeCode-Bible	Cursor rule	42	7d ago	none	A	128	Cursor
javascript-typescript-code-styleWebDevPeterGriffin/The-VibeCode-Bible	Cursor rule	42	7d ago	none	A	88	Cursor