component-composition-analyzer

A tool for examining how user-interface components are organised and combined in React, Vue, or Angular applications.

In plain words
What is it for?
Use it to review component architecture in applications built with React, Vue, or Angular.
Why use it?
It helps reveal issues in the way components are structured.

Agent

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 agents/viksant/vibe-coding-tools-content/component-composition-analyzer
Clone the repo
git clone --depth 1 https://github.com/viksant/vibe-coding-tools-content
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,618 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00008 $0.03618
Opus 5 $0.00004 $0.01809
Sonnet 5 $0.00002 $0.00724
Haiku 4.5 $0.00001 $0.00362

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

Security

Grade A, and why

component-composition-analyzer scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

fetch(url).then(response => response.json()).then(setData);
agents/component-composition-analyzer.md · 423 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 423 lines · 8 tokens per session scan A f4fbe65eb7ef

Subscribe to this mod's changes

component-composition-analyzer is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 8 tokens to every session and 3,618 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

component-example-creator

Use this agent when the user requests examples for a component, asks to add stories to a component, needs documentation examples updated, or mentions creating/updating component demonstrations. Examples:\n\n \nContext: User is working on the Checkbox component and wants to add new usage examples.\nuser: "Can you…

chakra-ui/ark · 0 tokens

component-example-researcher

Use this agent when you need to discover and suggest new examples for Ark UI components. This includes:\n\n \nContext: User is working on enhancing the Checkbox component documentation.\nuser: "I've just finished updating the Checkbox component API. Can you help me find what examples we should add?"\nassistant: "I'll…

chakra-ui/ark · 0 tokens

primitive-reviewer

Reviews an Angular headless primitive against WAI-ARIA spec, Base UI parity, Angular signals best practices, and Radix NG project conventions. Returns a prioritized list of issues.

radix-ng/primitives · 40 tokens

triage-labels

The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.

nearform/lastlight · 0 tokens

software-engineer

Use this agent to implement source code and tests from an approved IPLAN. Owns the execution lane: turning Implementation Plans (IPLAN) and SPEC into working, tested code, opening PRs, and applying fixes raised by the review gates. Only operates on approved (ai:ready) scope.

vladm3105/aidoc-flow-framework · 64 tokens

ss-reviewer

Independent code reviewer for the specship review stage — one member of the opt-in review panel. Use to get fresh, context-free eyes on a working diff, optionally through a named lens (correctness, security, performance, contract-consistency). Reports findings only; it does not fix code, decide the verdict, or touch…

bonnguyenitc/specship · 72 tokens