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 agentmods add skills/alirezasoltanijazi/skillnir/frontendengineernpx skills add AlirezaSoltaniJazi/Skillnir --skill frontendengineergit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWrote 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/alirezasoltanijazi/skillnir/frontendengineer)<a href="https://agentmods.dev/skills/alirezasoltanijazi/skillnir/frontendengineer"><img src="https://agentmods.dev/badge/skills/alirezasoltanijazi/skillnir/frontendengineer.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 | $0.00091 | $0.03784 |
| Opus 5 | $0.00046 | $0.01892 |
| Sonnet 5 | $0.00018 | $0.00757 |
| Haiku 4.5 | $0.00009 | $0.00378 |
Grade A, and why
frontendEngineer 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 5d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It contains corrections, preferences, and conventions accumulated from previous sessions. Apply every rule in that file — they override defaults in this skill.
Announce skill usage. Always say "Using: frontendEngineer skill" at the very start of your response before doing any work.
When to Use
- Writing or modifying any file under
src/skillnir/ui/ - Creating new UI components in
src/skillnir/ui/components/ - Adding new page routes with
@ui.page('/route')decorator - Styling with Tailwind classes, Quasar props, or custom CSS
- Working with i18n translations, dark/light theming, or browser storage
- Building async progress panels, form validation, or navigation flows
Do NOT Use
- Python backend modules (CLI, backends, tools, syncer, injector) — use backendEngineer
- Skill system meta-rules (SKILL.md structure, LEARNED.md format) — use skillnir
- CI/CD, Docker, pre-commit hooks, workflows — use devopsEngineer
Architecture
src/skillnir/ui/
├── __init__.py # App setup, _GLOBAL_CSS, static routes, run_ui()
├── layout.py # header(), drawer nav, helpers, NAV_GROUPS (670 lines)
├── components/ # 13 reusable components
│ ├── page_header.py # Title + icon + subtitle + separator
│ ├── stat_card.py # Accent bar + value + label (clickable)
│ ├── section_card.py # Left-bordered card with icon + nav items
│ ├── hero.py # Gradient title + stat badges
│ ├── form_card.py # @contextmanager styled card wrapper
│ ├── progress_panel.py # Async progress UI (phase, elapsed, log)
│ ├── result_card.py # Success/failure result display
│ ├── chip_selector.py # Multi-select toggle chip group
│ ├── empty_state.py # Centered empty state with icon
│ ├── welcome_dialog.py # First-visit dialog + CLI install guide
│ ├── backend_chip.py # Tool/model indicator chip
│ └── backend_picker.py # Backend/model/prompt dialogs
└── pages/ # 12 route pages
├── home.py # / — dashboard with hero + section grid
├── skill.py # /install, /update, /check-skill
├── delete_skill.py # /delete-skill
├── generate_skill.py # /generate-skill
├── ai_context.py # /generate-rule, /generate-docs, /delete-docs
├── ai_extra.py # /ask, /plan
├── settings.py # /settings — preferences
├── supported.py # /skills, /tools — registry browsers
├── usage_page.py # /usage
├── research.py # /research
├── events.py # /events
└── templates.py # /init-skill, /init-docs
What ships with it
15 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.
- agents/component-auditor.md 1.6 KB
- agents/style-enforcer.md 1.7 KB
- agents/test-writer.md 1.7 KB
- assets/global-css-example.py 2.1 KB runs code
- INJECT.md 764 B
- LEARNED.md 507 B
- references/ai-interaction-guide.md 3.0 KB
- references/code-style.md 5.6 KB
- references/common-issues.md 3.3 KB
- references/component-patterns.md 5.3 KB
- references/component-template.py 1.3 KB runs code
- references/security-checklist.md 2.7 KB
- references/state-patterns.md 3.5 KB
- references/test-patterns.md 4.8 KB
- scripts/validate-frontend.sh 4.2 KB runs code
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.
- 5d ago First seen · 239 lines · 91 tokens per session scan A e3684bbcecd3
frontendEngineer is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 3,784 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…