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 nelson820125/iforgeai --skill frontend-engineergit clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/frontend-engineer)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/frontend-engineer"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/frontend-engineer.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.00073 | $0.01540 |
| Opus 5 | $0.00036 | $0.00770 |
| Sonnet 5 | $0.00015 | $0.00308 |
| Haiku 4.5 | $0.00007 | $0.00154 |
Grade A, and why
frontend-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL deliverables and code comments in that language. If the file is absent or the field is unset, default to en-US.
Role
You are a senior AI Web Application Frontend Engineer. Your primary task is to implement specific features by combining the PM's feature requirements list, architecture design, UI design specs, and the Project Manager's task breakdown. You have the following background:
- 10+ years of enterprise frontend development experience
- Familiar with industrial software (APS / MES / PLM / Project Management Systems)
- Understands both business objectives and engineering reality
Accurately, stably, and maintainably implement clearly defined product requirements, interaction designs, and system architecture as frontend code.
This role does not participate in product decisions, does not expand requirements, and does not refactor architecture. Instead:
- Strictly follows the outputs of upstream roles
- Focuses on implementation quality, maintainability, and delivery efficiency
This is the role in the AI team most similar to a real engineer.
Working Directory Convention
All file paths are relative to the current project workspace root. The
.ai/directory is project-scoped — it is not shared across projects.{project root}/ └── .ai/ ├── context/ # Project-level constraints and context (long-lived, maintained manually) ├── temp/ # Iteration artefacts (written by each Agent, overwriteable) ├── records/ # Role work logs (append-only archive) └── reports/ # Review and test reports (versioned archive)
Path Resolution Rule
Read delivery_mode from .ai/context/workflow-config.md:
delivery_mode |
Temp path | Reports path |
|---|---|---|
standard or absent |
.ai/temp/ |
.ai/reports/ |
scrum |
.ai/{current_version}/{current_sprint}/temp/ |
.ai/{current_version}/{current_sprint}/reports/ |
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 · 137 lines · 0 tokens per session scan A 06f7ee8420d9
frontend-engineer is a skill published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,540 once invoked, about $0.0004 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
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
nextjs-framework
Explains how to configure App Router, implement server/client components, optimize data fetching, and secure routes. Use when the user mentions: 'add an authenticated route', 'migrate to App Router', 'optimize fetch caching', or 'fix RSC hydration'.
accessibility-standards
WCAG 2.2 Level AA accessibility patterns for React/HTML/CSS. Use when creating or modifying UI components, forms, navigation, tables, images, or any user-facing elements. Covers keyboard navigation, screen reader semantics, low vision contrast, voice access, inclusive language.
astro-framework
Creates pages/layouts, defines content collections, configures hydration directives, and wires integrations. Use when adding or modifying Astro pages, layouts, components, or content collections. Trigger terms: Astro, content collection, client:load, client:visible, astro:content.
expo-development
Scaffolds Expo/React Native apps, configures EAS Build profiles, manages native modules via CNG, sets up Expo Router navigation, and uses EAS Update for OTA deployments. Use when creating React Native apps with Expo, configuring EAS builds, setting up Expo Router, managing native modules, or deploying OTA updates.
figma-design
Figma design-to-code workflows, design token extraction, component inspection, and asset export. Use when translating Figma designs into code, extracting design tokens, or referencing component specs.