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 ambient-code/platform --skill developmentgit clone --depth 1 https://github.com/ambient-code/platformWrote 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/ambient-code/platform/development)<a href="https://agentmods.dev/skills/ambient-code/platform/development"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/development/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/ambient-code/platform/development"><img src="https://agentmods.dev/badge/skills/ambient-code/platform/development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.00469 |
| Opus 5.5 | $0.00027 | $0.00188 |
| Sonnet 5.5 | $0.00013 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
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 1mo 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 Development
Before writing or changing any frontend code, load the project's frontend standards. These are non-negotiable constraints — not suggestions.
User Input
$ARGUMENTS
Required Reading
Read all files in specs/standards/frontend/ before proceeding:
ls specs/standards/frontend/
At minimum, this includes:
specs/standards/frontend/conventions.spec.md— zero-tolerance rules (noany, Shadcn only, React Query for all data,typeoverinterface, colocated components, feature flags)specs/standards/frontend/react-query.spec.md— file structure (ports/adapters/queries), data fetching patterns, testing requirements, validation checklist
Also read the API adapter spec if working on the services layer:
specs/frontend/api-adapter.spec.md— port interface contract, canonical types, 30 API domains, testability requirements
Key Constraints
These apply to every frontend change, no exceptions:
- Zero
anytypes. Use proper types orunknown. - Shadcn UI components only. No custom buttons, inputs, dialogs.
- React Query for all data fetching. No manual
fetch()in components. typeoverinterface. Always.- All adapters must be tested. No adapter merged without unit tests using recorded responses.
- All hooks must be tested. Hook tests use mock adapters, not real backends.
- Port interfaces, not raw API calls. React Query hooks consume ports, not
services/api/directly.
After Reading
Confirm you have loaded the standards, then proceed with the task. If any of your changes would violate these constraints, stop and discuss with the user before writing code.
What ships with it
1 file 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.
- 1mo ago First seen · 54 lines · 67 tokens per session scan A 99c523b7c0bd
frontend-development is a skill published in the GitHub repository ambient-code/platform (131 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 469 once invoked, about $0.0003 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-30.
Other skills, from other repositories
openforms-mui
Author, render, preview and debug OpenForms FormSchemaJSON form definitions as idiomatic, themed, accessible MUI (React). Use when the user wants to design an OpenForms form, render an OpenForms schema with Material UI, convert an OpenForms JSON schema into a React MUI form, preview a form schema, or debug…
canvas-webapp
Render a React/Vite (or any bundled) web app on the pi-dashboard canvas, which loads loopback URLs in a sandboxed opaque-origin iframe. Use when a canvas(target:{kind:"url"|"server"}) target shows up blank white, an empty surface, or a /live/ 500 ECONNREFUSED. Covers why Vite dev servers and non-CORS static servers…
create-custom-widget
Build a Mendix pluggable widget from scratch with React and TypeScript and package it as an .mpk. Use when no marketplace or built-in widget covers what is needed and a custom React component has to be written.
react-application-structure
Establishes or reviews the directory layout, feature boundaries, state design, routing approach, and data-fetching conventions for a React 18+ TypeScript application. Invoked when the user asks to structure a React app, set up a scalable architecture, or review React project organization.
react-component-design
Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.
next-application-structure
Establishes or reviews directory layout, server/client boundaries, routing, data-fetching strategy, and testing structure for Next.js 14+ App Router TypeScript applications. Invoked when the user asks to structure a Next app, set App Router conventions, or review architecture for React parity.