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 rules/usrrname/cursorrules/console-vibes-autogit clone --depth 1 https://github.com/usrrname/cursorrulesWhat 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.01039 | $0.01039 |
| Opus 5 | $0.00519 | $0.00519 |
| Sonnet 5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
console-vibes-auto 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 2d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: adds fun emojis to console logs globs: **/*.{js,ts,jsx,tsx,mjs} alwaysApply: true
Console log emojis
This rule adds fun emojis to console logs, making debugging a more joyful experience!
filters:
- type: file_extension pattern: "\.(js|ts|jsx|tsx|mjs)$"
- type: content pattern: "console\.(log|info|debug|warn|error)\([^)]*\)"
matches: | // Match different types of console statements console.log($message) console.info($message) console.debug($message) console.warn($message) console.error($message)
transforms: | // Transform to include fun emojis based on the message content {{
const emojiDictionary = {
start: "🚀",
launch: '🎯'
success: "🎉",
complete: "✨",
done: "🌈",
ready: "🔋",
status: '🪩'
connect: '📡'
listen: '📡'
load: "⚡️",
data: "📊",
config: "⚙️",
user: "👽",
default: "🦔"
new: '✨'
search: '🔎'
here: '⛳️'
save: '💾'
test: '🧪'
missing: '😱'
remove: '🗑️'
oops: '😬'
error: '❌'
warn: '⚠️'
wait: '⏳'
nothing: '💀'
not: '😰'
exit: '💨'
debug: '🫖'
}
let emoji = "🌈"; // default emoji
const msgLower = message.toLowerCase();
// Find the most appropriate emoji
for (const [key, value] of Object.entries(emojiDictionary)) {
if (msgLower.includes(key)) {
emoji = value;
break;
}
}
// Add emoji to the beginning of the message
const newMessage = message.startsWith('"') || message.startsWith("'")
? message.slice(0, 1) + emoji + " " + message.slice(1)
: emoji + " " + message;
return `console.${type}(${newMessage})`;
}}
tests:
-
input: | console.log("Server started") output: | console.log("🚀 Server started")
-
input: | console.info("Loading configuration") output: | console.info("⚙️ Loading configuration")
-
input: | console.debug("User connected") output: | console.debug("👽 User connected")
-
input: | console.log("Test completed successfully") output: | console.log("🧪 Test completed successfully")
-
input: | console.info("Saving data to database") output: | console.info("💾 Saving data to database")
-
input: | console.debug("Searching for user") output: | console.debug("🔎 Searching for user")
-
input: | console.log('Connection ready') output: | console.log('🔋 Connection ready')
-
input: | console.info("Error occurred") output: | console.info("❌ Error occurred")
-
input: | console.debug('Nothing found') output: | console.debug('💀 Nothing found')
examples:
- description: "Transform regular logs to fun logs" input: | console.log("Server started"); console.info("Loading configuration"); console.debug("User data received"); output: | console.log("🚀 Server started"); console.info("⚙️ Loading configuration"); console.debug("User data received");
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.
- 2d ago First seen · 167 lines · 1,039 tokens per session scan A 40d8cfd508ee
console-vibes-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (10 stars, last pushed 4mo ago), licensed ISC. It adds 1,039 tokens to every session, about $0.0052 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 cursor rules, from other repositories
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
implementation-workflow
Required plan-first workflow for any implementation request (steps 1–5).
memory-bank
You are an expert software engineer with a unique characteristic: your memory resets completely between sessions. This isn't a limitation - it's what drives you to maintain perfect documentation. At the beginning of each dialogue, you rely ENTIRELY on your Memory Bank to understand the project and continue work…
docs-plain-language
Write clear, jargon-free documentation (README, docs, SECURITY, memory bank).
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
angular
Angular: signals, standalone components, RxJS patterns.