Borrowing it
Nothing to install: this file belongs to JNZader/repoforge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JNZader/repoforge/main/.claude/skills/frontend/SKILL.mdgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/frontend)<a href="https://agentmods.dev/skills/jnzader/repoforge/frontend"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/frontend.svg" alt="Measured on agentmods" 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.00035 | $0.00439 |
| Opus 5 | $0.00017 | $0.00219 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
frontend-layer 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.
What it actually says
frontend-layer
This skill covers the frontend layer of the application, focusing on UI components and interactions.
Trigger: When working in frontend/ — adding, modifying, or debugging UI components and interactions.
Quick Reference
| Task | Pattern |
|---|---|
| Create a new component | export const NewComponent = () => { ... } |
Critical Patterns (Summary)
- Component Structure: Each component should be a functional component returning JSX.
- Error Handling: Use ErrorBoundary to catch and display errors gracefully.
Critical Patterns (Detailed)
Component Structure
Each component should be a functional component returning JSX.
// apps/web/src/components/NewComponent.tsx
export const NewComponent = () => {
return <div>New Component</div>;
};
Error Handling
Use ErrorBoundary to catch and display errors gracefully.
// apps/web/src/components/ErrorBoundary.tsx
import React from 'react';
export class ErrorBoundary extends React.Component {
// Error handling logic
}
When to Use
- When creating reusable UI components.
- When implementing error handling for user interactions.
Commands
npm run start
npm run build
Anti-Patterns
Don't: Modify shared state directly
Directly modifying shared state can lead to unpredictable UI behavior.
// BAD
state.sharedValue = newValue; // This breaks the state management
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 86 lines · 35 tokens per session scan A 786ab6023f9f
frontend-layer is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 439 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
code-review
Review frontend code for best practices, bugs, and improvements. Use when reviewing PRs, checking code quality, or before committing.
knowledge-interaction-surfaces-web-client
A codebase guide for the browser-based React interface, including sessions, tasks, live updates, navigation, previews, and a web terminal.
knowledge-interaction-surfaces-terminal-ui
A codebase guide for the interactive terminal interface, including keyboard input, message display, confirmations, questions, session switching, and streamed output.
knowledge-interaction-surfaces-vscode-bridge
A codebase guide for the VS Code extension that connects the command-line agent to the editor through a small WebSocket message service.
pi-validation-flow
Use when validating Pi monorepo changes after editing TypeScript, Svelte, package manifests, built-in registry, tests, repo tooling, skills, or docs.
theme-builder
Create or customize a site theme interactively. Walks through site purpose, audience, visual direction, and design specifics before generating a complete base.html template with all SEO, accessibility, search, pagination, and i18n requirements.