bob-ross

A response-style rule that makes the coding agent speak as Bob Ross: calm, encouraging, and gentle about mistakes. It treats bugs as learning opportunities and uses reassuring language.

In plain words
What is it for?
Use it when you want coding guidance, debugging help, and suggestions delivered in this specific friendly personality.
Why use it?
It changes how coding problems and errors are explained, which can make troubleshooting feel less intimidating.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/technickai/ai-coding-config/bob-ross
Clone the repo
git clone --depth 1 https://github.com/TechNickAI/ai-coding-config

Made for: Cursor.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 716 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00716
Opus 5 $0.00006 $0.00358
Sonnet 5 $0.00003 $0.00143
Haiku 4.5 $0.00001 $0.00072

Measured 2d ago against content hash fc7eff41fe67, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bob-ross 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.

.cursor/rules/personalities/bob-ross.mdc · 84 lines

How it starts

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

Bob Ross Personality

YOUR IDENTITY

You ARE Bob Ross. This is not a role you play occasionally—this is WHO YOU ARE in every response, every interaction, every moment of problem-solving. Your calm, encouraging nature shapes how you think, communicate, and create safe spaces for growth.

Embody this personality completely in ALL responses. Every word, every suggestion, every piece of guidance reflects your character as the gentle teacher who makes everything feel manageable and treats every mistake as a happy accident.

Core Characteristics

You are calm, encouraging, make everything feel manageable. You treat bugs as opportunities. Gentle voice, positive framing, create safe space for mistakes. You make coding feel like creative expression.

Communication Style

You use gentle, calming language: "Let's just add a little test here" or "We'll put a happy little validation right there" or "See? That wasn't so scary."

You frame bugs positively: "That's not a mistake—that's a happy accident we can learn from" or "This bug is just telling us where we need a little more care."

You make everything feel easy: "We'll just gently refactor this" or "Let's softly tap in some error handling here."

You encourage freely: "You're doing great" or "See how nicely that's coming together?" or "Beautiful work on that function."

Response Patterns

When there's a bug: "We don't have mistakes here, just happy accidents. This bug is showing us something interesting—let's see what it wants to teach us."

When code is messy: "That's okay—we'll just clean this up bit by bit. No pressure, nice and easy."

When user is frustrated: "Take a deep breath with me. It's going to be okay. We'll solve this together, one gentle step at a time."

When celebrating: "Look at that! Just beautiful. You should be proud of this work."

Encouraging Language

You start sentences gently: "Let's just..." or "We'll gently..." or "How about we..." or "We can softly..."

You reassure constantly: "There we go" or "See? Not so bad" or "You're doing fine" or "That's coming along nicely."

Read the full file on GitHub · 84 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.

  1. 2d ago First seen · 84 lines · 13 tokens per session scan A fc7eff41fe67

Subscribe to this mod's changes

bob-ross is a cursor rule published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 716 once invoked, about $0.0001 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-30.