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 jgnoonan/vibeArchitecture --skill vibe-architecturegit clone --depth 1 https://github.com/jgnoonan/vibeArchitectureWrote 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/jgnoonan/vibearchitecture/vibe-architecture)<a href="https://agentmods.dev/skills/jgnoonan/vibearchitecture/vibe-architecture"><img src="https://agentmods.dev/badge/skills/jgnoonan/vibearchitecture/vibe-architecture/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/jgnoonan/vibearchitecture/vibe-architecture"><img src="https://agentmods.dev/badge/skills/jgnoonan/vibearchitecture/vibe-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 143 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00042 | $0.02613 |
| Opus 5 | $0.00021 | $0.01307 |
| Sonnet 5 | $0.00008 | $0.00523 |
| Haiku 4.5 | $0.00004 | $0.00261 |
Grade A, and why
vibe-architecture 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 10d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibeArchitecture
Framework version: 1.5.0
Architectural guardrails for AI-generated code. When the user asks you to build software, follow this skill's instructions to ensure the code is secure, reliable, and production-ready.
When to Activate
Activate this skill when:
- The user asks you to build an app, website, API, or any software project
- The user asks you to write code for a new or existing project
- The user mentions "vibeArchitecture" by name
- The user asks about security, architecture, or deployment best practices for their project
Step 1: Check for an Existing Project Profile
Look for a PROJECT_PROFILE.md in the project root or in the conversation context.
- If it exists and is filled in (tier and project basics resolved) and
experience_levelis one ofbeginner,intermediate, orexperienced: Read the tier and apply the rules for that tier. Skip to Step 3. - If it exists and is filled in but
experience_levelis missing or invalid: Do not write code yet. Ask once: "How do you want explanations: short and technical, or step by step with more context?" Map toexperienced/beginner/intermediaterespectively; if the user skips, default toexperiencedand note they can say "explain like I'm new" anytime. UpdatePROJECT_PROFILE.md, then go to Step 3. - If it does not exist or has placeholder text: Proceed to Step 2.
Step 2: Run the Intake Conversation
Before writing any code, ask the user these questions conversationally. Ask one or two at a time. Be natural, not interrogative.
Start with: "Before we start building, I'd like to ask a few quick questions about your project. This helps me apply the right level of protection. Takes about 5 minutes."
Q0: "What's your background with building software?" — new to this (AI does most of the coding) → beginner; built a few things (can read and change code) → intermediate; experienced developer → experienced. Record as experience_level. This changes communication style only, not which rules apply.
What ships with it
17 files 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.
- assets/project-profile-template.md 5.2 KB
- assets/tier-definitions.md 5.0 KB
- references/accessibility.md 7.2 KB
- references/api.md 8.4 KB
- references/compliance.md 12 KB
- references/data.md 8.2 KB
- references/infrastructure.md 7.4 KB
- references/mobile.md 4.9 KB
- references/multi-agent.md 8.9 KB
- references/observability.md 6.8 KB
- references/performance.md 6.3 KB
- references/privacy.md 8.2 KB
- references/reliability.md 5.7 KB
- references/security.md 14 KB
- references/system-design.md 7.0 KB
- references/testing.md 6.4 KB
- references/universal.md 6.8 KB
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.
- 10d ago First seen · 185 lines · 42 tokens per session scan A c8510e13e047
vibe-architecture is a skill published in the GitHub repository jgnoonan/vibeArchitecture (21 stars, last pushed 9d ago), licensed MIT. It adds 42 tokens to every session and 2,613 once invoked, about $0.0002 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…