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 pyros-projects/limitless --skill vibe-checkergit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/vibe-checker)<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.
<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>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.00104 | $0.00788 |
| Opus 5.5 | $0.00042 | $0.00315 |
| Sonnet 5.5 | $0.00021 | $0.00158 |
| Haiku 4.5 | $0.00010 | $0.00079 |
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 1mo 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 — 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
-
Read the whole thing as one experience. Move through the product, flow, or artifact in order instead of judging isolated pieces first.
-
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
-
Name the mismatch clearly. Avoid generic "vibe" language. Point to the specific break: warm to cold, playful to legalistic, confident to apologetic.
-
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 coherentWhere the mood shiftsWhy the shift mattersWhat emotional direction should leadHow 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.
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.
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.
- 1mo ago First seen · 97 lines · 104 tokens per session scan A c850440445e8
vibe-checker is a skill published in the GitHub repository pyros-projects/limitless (2 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 788 once invoked, about $0.0004 per session on Opus 5.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
brand-identity
Brand strategy and identity design for businesses and products. Use when creating brand guidelines, developing visual identity systems, or defining brand positioning.
graphic-design
Professional graphic design principles for digital and print media. Use when creating visual designs, choosing color palettes, typography, layouts, or providing design feedback.
generic-react-ux-designer
Professional UI/UX design expertise for React applications. Covers design thinking, user psychology (Hick's/Fitts's/Jakob's Law), visual hierarchy, interaction patterns, accessibility, performance-driven design, and design critique. Use when designing features, improving UX, solving user problems, or conducting design…
frontend-enhancer
Enhance the visual design of web apps: modern UI components, layout, responsive design, color palettes, animations. Use for styling and UI polish; pair with ui-research first for new design directions.
generic-design-system
Complete design system reference for any project - colors, typography, spacing, components, animations. Adapts to project theme and tech stack. Use when implementing UI, choosing colors, creating animations, or ensuring brand consistency. For new design systems, use ui-research skill first.
generic-react-design-system
Complete design system reference for React applications. Covers colors, typography, spacing, component patterns, glassmorphism effects, GPU-accelerated animations, and WCAG AA accessibility. Use when implementing UI, choosing colors, applying spacing, creating components, or ensuring brand consistency.