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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill component-analysisgit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/component-analysis)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/component-analysis"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/component-analysis/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/j-star-films-studios/vibecode-protocol-suite/component-analysis"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/component-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00648 |
| Opus 5 | $0.00010 | $0.00324 |
| Sonnet 5 | $0.00004 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
component-analysis 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 7d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Analysis Skill
Analyze components for coding standards compliance and provide actionable improvements.
When to Use
- Refactoring discussions
- Before major component changes
- When asked to "analyze" or "audit" a component
- Code review of specific files
Analysis Process
1. Identify Component
Get from user or extract:
- Component Path: Full file path
- Component Name: The component name
2. Initial Examination
Read file and check:
- Code structure and organization
- Purpose and functionality
- Immediate issues
- Total lines (check 200-line rule)
3. Coding Guidelines Check
| Check | What to Look For |
|---|---|
| Size | < 200 lines (refactor if exceeded) |
| Single Responsibility | Does one thing well |
| TypeScript | Proper types, interfaces for props |
| Naming | PascalCase components, camelCase functions, handle* events |
| Hooks | Proper use of React hooks and effects |
| Documentation | TSDoc/JSDoc comments |
| Imports | Organized, no unused imports |
4. Styling Check
| Check | What to Look For |
|---|---|
| Tailwind v4 | Using @theme integration |
| Color Tokens | Using primary, accent, semantic tokens |
| Responsive | Mobile-first (sm:, md:, lg:) |
| Dark Mode | dark: variants |
| Performance | Avoiding expensive backdrop-filter |
5. Mobile-First Check
- Mobile-first breakpoints
- Touch-friendly interactions
- Responsive typography
- Container responsiveness
6. Generate Report
# Component Analysis: [Name]
**File:** `[path]`
**Lines:** [X] / 200 max
**Score:** [X]/10
## ✅ Compliant
- [Things done well]
## ⚠️ Warnings
- [Minor issues]
## ❌ Violations
- [Critical issues]
## 📋 Recommendations
### High Priority
1. [Critical fix]
### Medium Priority
1. [Improvement]
## 🔧 Suggested Fixes
[Before/After code examples]
7. Offer Next Steps
- A) Implement high-priority fixes
- B) Create feature documentation
- C) Refactor if > 200 lines
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.
- 7d ago First seen · 104 lines · 19 tokens per session scan A 951d1b647192
component-analysis is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed today), licensed ISC. It adds 19 tokens to every session and 648 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-09-03.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
compiler-review
Review Rust port code for port fidelity, convention compliance, and error handling. Compares against the original TypeScript source.
ss-lint
Quick automated lint — detects common design system violations in seconds.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.