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 Ampli-Group/agentic-mobile-blueprint --skill frontend-developmentgit clone --depth 1 https://github.com/Ampli-Group/agentic-mobile-blueprintWrote 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/ampli-group/agentic-mobile-blueprint/frontend-development)<a href="https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/frontend-development"><img src="https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/frontend-development.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.00041 | $0.00672 |
| Opus 5 | $0.00020 | $0.00336 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
frontend-development 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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Development
Stack
Next.js 16 (App Router, Turbopack), React 19, Tailwind CSS v4, Zustand 5, TanStack Query v5, react-hook-form + Zod 4, TypeScript strict mode.
Imports
Use @/ path alias for src/: @/lib/supabase, @/components/Button.
Client vs Server
Mark interactive/stateful components with 'use client'. Default is server component.
Styling
Tailwind CSS v4 with @theme tokens in src/app/globals.css:
@import 'tailwindcss';
@theme {
--color-cream: #FCFAF7;
--color-slate-deep: #1B2030;
--color-emerald-glow: #10B981;
}
Add new design tokens in @theme, not in config files.
Supabase Clients
Three clients for different contexts:
| Import | Use for | Context |
|---|---|---|
@/lib/supabase |
General public queries | Client, graceful fallback if env missing |
@/lib/supabase-browser |
Auth flows (login, signup) | Client ('use client') |
@/lib/supabase-admin |
Admin operations | Server-only, createAdminClient() |
// Client component — auth flow
import { supabaseBrowser } from '@/lib/supabase-browser';
// Server component / action — admin
import { createAdminClient } from '@/lib/supabase-admin';
const supabase = createAdminClient();
State Management
Zustand with persist middleware. Use partialize to persist only selected fields:
import { create } from 'zustand';
import { persist } from 'zustand/middleware';
export const useMyStore = create(
persist(
(set) => ({
value: '',
setValue: (v: string) => set({ value: v }),
}),
{ name: 'my-store', partialize: (s) => ({ value: s.value }) }
)
);
Providers
Composed in src/app/layout.tsx. Order: QueryProvider → PostHogProvider → children. Add new providers inside QueryProvider.
Forms
Use react-hook-form + @hookform/resolvers + Zod for validation:
import { useForm } from 'react-hook-form';
import { zodResolver } from '@hookform/resolvers/zod';
import { z } from 'zod';
const schema = z.object({ email: z.string().email() });
const { register, handleSubmit } = useForm({
resolver: zodResolver(schema),
});
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.
- 8d ago First seen · 97 lines · 41 tokens per session scan A 5ca20d865c7a
frontend-development is a skill published in the GitHub repository Ampli-Group/agentic-mobile-blueprint (4 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 672 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
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…
rn-app-builder
A build workflow for React Native mobile apps, including Expo setup, shared code in a monorepo, login routing, APIs, themes, and releases. A monorepo stores multiple related packages in one code repository.
frontend-ui-dark-ts
Build dark-themed React applications using Tailwind CSS with custom theming, glassmorphism effects, and Framer Motion animations. Use when creating dashboards, admin panels, or data-rich interfaces with a refined dark aesthetic.
writing-react-native-storybook-stories
Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for…
setup-react-native-storybook
Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a…
upgrading-react-native-storybook
Incrementally upgrade React Native Storybook across the supported migration paths. Use when upgrading @storybook/react-native projects from 5.3.x to 6.5.x, 6.5.x to 7.6.x, 7.6.x to 8.3.x, 8.x to 9.x, or 9.x to 10.x. Detect the currently installed Storybook version, choose only the next migration step, update…