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.
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/plugins/googilyboogily/googilyboogily-claude-power-tools/frontend-agents)<a href="https://agentmods.dev/plugins/googilyboogily/googilyboogily-claude-power-tools/frontend-agents"><img src="https://agentmods.dev/badge/plugins/googilyboogily/googilyboogily-claude-power-tools/frontend-agents/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/plugins/googilyboogily/googilyboogily-claude-power-tools/frontend-agents"><img src="https://agentmods.dev/badge/plugins/googilyboogily/googilyboogily-claude-power-tools/frontend-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
frontend-agents 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 9d 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.
What it actually says
{
"name": "frontend-agents",
"description": "Frontend expert subagents for accessibility, CSS/styling, and Flutter cross-platform development",
"version": "1.0.0",
"author": {
"name": "GoogilyBoogily"
}
}
What it installs
The manifest is a name and a version. 3 agents travel with it, and installing the plugin installs all of them — 170 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 9d ago First seen · 9 lines scan A 08aaf5c472de
frontend-agents is a plugin published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
gluestack
Validation and quality enforcement for gluestack-ui projects with component patterns, accessibility, and theming skills. Includes MCP server for component discovery and source code retrieval.
frontend-mobile-development
Frontend UI development and mobile application implementation across platforms.
frontend-design
Frontend design skill for UI/UX implementation.
aio-visual-diff
Verify AI-built UI against design via measurement-driven diff — extracts computed CSS and bounding boxes through Chrome DevTools MCP, diffs against Figma reference or a frozen baseline, and feeds numerical deltas back to the agent. No screenshot eyeballing.
frontend-design
Astro, frontend design, and web design guidelines skills.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.