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 ytunahankskn/oh-meine-excode --skill frontend-squadgit clone --depth 1 https://github.com/ytunahankskn/oh-meine-excodeWrote 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/ytunahankskn/oh-meine-excode/frontend-squad)<a href="https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/frontend-squad"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/frontend-squad/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/ytunahankskn/oh-meine-excode/frontend-squad"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/frontend-squad.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00029 | $0.00442 |
| Opus 5.5 | $0.00012 | $0.00177 |
| Sonnet 5.5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
frontend-squad 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 2mo 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Squad
Use this skill for React, Next.js, or other frontend work when the user explicitly wants multi-agent collaboration.
The goal is not "more agents"; the goal is faster progress with less collision.
Frontend Split Strategy
Split along visual or structural boundaries, not arbitrary file counts.
Good splits:
- route shell vs feature section
- shared component updates vs page composition
- data wiring vs visual polish
- implementation vs verification
Bad splits:
- two workers editing the same component tree
- delegating the exact next blocking step away from the main agent
- parallelizing a tiny one-file change
Recommended Flow
- Main agent inspects framework, styling system, and target files.
- Main agent decides the visual direction and integration plan.
- Spawn an
explorerif codebase conventions are unclear. - Spawn up to two
workeragents with disjoint ownership when the task has independent slices. - Main agent handles shared glue, final polish, and verification.
Suggested Worker Roles
Worker A: Structure
Owns:
- route/page files
- layout composition
- section ordering
- data and prop wiring
Worker B: Components
Owns:
- reusable UI components
- styling tokens
- motion or micro-interactions
- responsive refinements
Optional Explorer: Conventions
Owns:
- identifying project patterns
- locating design system primitives
- tracing existing component usage
Required Checks
- Match the existing framework and styling patterns.
- Preserve responsive behavior.
- Avoid generic UI choices when the task asks for strong frontend work.
- Run the relevant build or test command when possible.
- Report visual or behavioral risks if full verification is not possible.
Prompt Template
When applying this skill, frame delegation like this:
"I will keep the integration path local. One worker owns the page shell and wiring, another owns reusable UI pieces and polish. If conventions are unclear, an explorer will map the existing patterns first."
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.
- 2mo ago First seen · 78 lines · 29 tokens per session scan A 6c348ee6369d
frontend-squad is a skill published in the GitHub repository ytunahankskn/oh-meine-excode (2 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 442 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
windows-appshot
Use when the user invokes $windows-appshot or asks to create a Windows appshot bundle, including foreground-window screenshots, UI Automation text, metadata.json, prompt.md, or appshots generated by scripts/New-Appshot.ps1.
stss
Reduce defensive disclaimers, stacked hedging, and self-protective narration when drafting, rewriting, or auditing proposals, articles, case studies, captions, and other reader-facing prose. Use when defensive wording is requested for review or appears in a draft, including wording the assistant adds. Preserve…
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
boss-briefing
Vault health check — workflow pattern analysis, profile sync, session gap recovery, persona rule proposals.
compact-kb
Use only when user explicitly invokes $compact-kb.
build-frontend
Build or modify frontend interfaces using repository-native components while preserving accessibility, responsive behavior, state handling, and visual verification. Use for UI features, design implementation, forms, client-side defects, and frontend refactors; do not use for backend-only or infrastructure-only work.