vibe-checker

vibe-checker is a skill for Claude Code from pyros-projects/limitless. It costs 104 tokens per session (788 once invoked), scanned A, original, MIT.

A review of whether a product, prototype, or workflow feels consistent in tone and mood from one part to the next.

In plain words
What is it for?
Use it to compare screens, user flows, copy, success messages, errors, and empty states, then describe what feels unified or out of place.
Why use it?
It identifies emotional mismatches that ordinary function, design, or usability checks may miss, such as friendly copy beside cold interactions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the after-hours plugin — 7 skills shipped together

Good fit Use it to compare screens, user flows, copy, success messages, errors, and empty states, then describe what feels unified or out of place.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pyros-projects/limitless/vibe-checker
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.

Any agent
npx skills add pyros-projects/limitless --skill vibe-checker
Clone the repo
git clone --depth 1 https://github.com/pyros-projects/limitless

Made for: Claude Code.

Or install after-hours, the plugin that ships this one along with the rest of its 7 skills.

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.

agentmods badge for vibe-checker

README.md
[![agentmods](https://agentmods.dev/badge/skills/pyros-projects/limitless/vibe-checker/github.svg)](https://agentmods.dev/skills/pyros-projects/limitless/vibe-checker)
Your own site
<a href="https://agentmods.dev/skills/pyros-projects/limitless/vibe-checker"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/vibe-checker/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.

agentmods 80×15 button for vibe-checker

Your own site · 80×15
<a href="https://agentmods.dev/skills/pyros-projects/limitless/vibe-checker"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/vibe-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 788 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00104 $0.00788
Opus 5 $0.00052 $0.00394
Sonnet 5 $0.00021 $0.00158
Haiku 4.5 $0.00010 $0.00079

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

Security

Grade A, and why

vibe-checker 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 9d 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.

plugins/after-hours/skills/vibe-checker/SKILL.md · 97 lines

How it starts

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

Vibe Checker

Overview

This skill reviews emotional coherence.

Not whether the thing functions. Not whether it passes a normal design checklist. Whether it feels like one product, with one point of view, made by one mind.

When to Use

Use this when:

  • the product works but somehow feels off
  • different screens or flows seem to come from different moods
  • the copy and UI are pulling in different directions
  • you want feedback beyond correctness and usability

Do not use this as a vague "vibes" machine. It should make specific observations with real implications.

What to Look For

Check for mismatches in:

  • tone of voice
  • emotional arc
  • interaction posture
  • friendliness vs coldness
  • playfulness vs bureaucracy
  • confidence vs apology

Then describe what feels unified, what feels split, and where the breaks are most visible.

Working Loop

  1. Read the whole thing as one experience. Move through the product, flow, or artifact in order instead of judging isolated pieces first.

  2. Track mood shifts. Notice where the tone, posture, or emotional temperature changes. Compare concrete pairs such as:

    • success tone versus error tone
    • empty state versus full state
    • first-screen confidence versus deep-settings confidence
    • the voice used when asking for information versus the voice used when delivering information
    • playful surfaces versus bureaucratic surfaces
  3. Name the mismatch clearly. Avoid generic "vibe" language. Point to the specific break: warm to cold, playful to legalistic, confident to apologetic.

  4. Recommend a unifying direction. The goal is not just to notice the split, but to help the work feel like one mind again.

Suggested Output Shape

  • What feels coherent
  • Where the mood shifts
  • Why the shift matters
  • What emotional direction should lead
  • How to bring the outliers back into tune

Tiny Example

  • What feels coherent: The homepage and onboarding both sound curious, calm, and inviting.
  • Where the mood shifts: The billing page abruptly becomes legalistic and defensive.
  • Why the shift matters: It makes the product feel less trustworthy right when money enters the room.
  • What emotional direction should lead: Keep the calm, competent voice.
  • How to bring the outliers back into tune: Rewrite billing copy so it stays direct and reassuring instead of procedural.

Read the full file on GitHub · 97 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 9d ago First seen · 97 lines · 104 tokens per session scan A c850440445e8

Subscribe to this mod's changes

vibe-checker is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 26d ago), licensed MIT. It adds 104 tokens to every session and 788 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

ux-spec

Generates UI/UX specifications with wireframes and design system. Creates UXSPEC.md and DESIGNSYSTEM.md from PRD and Architecture specs. Use when designing app interface and creating design system.

rshankras/claude-code-apple-skills · 41 tokens

liquid-glass

Implement Liquid Glass design using .glassEffect() API for iOS/macOS 26+. Covers SwiftUI, AppKit, UIKit, and WidgetKit. Use when creating modern glass-based UI effects.

rshankras/claude-code-apple-skills · 45 tokens

app-icon-generator

Generates an app icon for macOS or iOS — a fast CoreGraphics placeholder and/or flat layered source art to finish in Icon Composer (the Liquid Glass / iOS 26+ standard). Produces appearance variants (light/dark/tinted) and installs into the asset catalog. Use when the user wants to create, generate, iterate, or update…

rshankras/claude-code-apple-skills · 80 tokens

onboarding-generator

Generates value-moment-first onboarding flows for iOS/macOS apps — the default architecture races a new user to the first felt experience of the app's promised outcome, branching on whether they can experience it right now or need to plan for later. The classic paged welcome-carousel tour is an explicit fallback for…

rshankras/claude-code-apple-skills · 93 tokens

ui-prototyping

Explore multiple divergent UI directions for a screen as named Swift.

rshankras/claude-code-apple-skills · 21 tokens

assistive-access

Assistive Access implementation for cognitive accessibility including simplified scenes, navigation icons, runtime detection, and design principles. Use when optimizing apps for Assistive Access mode.

rshankras/claude-code-apple-skills · 35 tokens