frontend

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.

Security

Grade A, and why

frontend 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 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.

plugins/frontend/.claude-plugin/plugin.json · 22 lines

What it actually says

{
  "name": "frontend",
  "version": "1.0.0",
  "description": "Use when adding or changing a feature, page, API call, hook, form, or component in a React or Next.js app laid out as infrastructure + domain + view + routes; when deciding which layer code belongs in; when reviewing a diff for layering violations; or when structuring a greenfield frontend. Covers dependency rules, naming, serialization boundaries, and typed errors.",
  "author": {
    "name": "João Vogler",
    "url": "https://github.com/jv-vogler"
  },
  "homepage": "https://github.com/jv-vogler/skills",
  "repository": "https://github.com/jv-vogler/skills",
  "license": "MIT",
  "keywords": [
    "frontend",
    "architecture",
    "react",
    "nextjs",
    "typescript",
    "clean-architecture"
  ],
  "skills": "./skills/"
}

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.

Related

Other plugins, from other repositories