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 isaacsight/kernel --skill higgsfield-websitesgit clone --depth 1 https://github.com/isaacsight/kernelWrote 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/isaacsight/kernel/higgsfield-websites)<a href="https://agentmods.dev/skills/isaacsight/kernel/higgsfield-websites"><img src="https://agentmods.dev/badge/skills/isaacsight/kernel/higgsfield-websites.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.00250 | $0.02350 |
| Opus 5 | $0.00125 | $0.01175 |
| Sonnet 5 | $0.00050 | $0.00470 |
| Haiku 4.5 | $0.00025 | $0.00235 |
Grade C, and why
higgsfield-websites scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh | sh How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Higgsfield website builder (CLI) — two product types, two flows
You drive the whole lifecycle through the Higgsfield CLI (higgsfield website …), then edit code on the local filesystem with git + bun. You are
building ONE per-website Cloudflare Worker: a React 19 + TanStack Start app,
server-rendered (SSR), deployed as a single Worker at the product's own
subdomain. The project lives in app/ — run every bun/build command from
there.
The two types — and the REQUIRED --type on create
higgsfield website create requires --type, and it is the USER'S choice —
when the request doesn't make it obvious, ask the user before creating (one
question, up front):
--type website— a standalone product with NO Higgsfield integration and NO AI generation of any kind (no image/video/audio/text generation — not via Higgsfield, and not via some other provider): no "Sign in with Higgsfield", no requests to Higgsfield, no fnf SDK. Every website gets a fully independent brand: own palette, type, and chrome from a design brief, custom Tailwind/CSS only — never import@higgsfield/quanta/*or use q-prefixed tokens anywhere, and no "Powered by / Built on Higgsfield" badges or mentions in page content. The user's brand is the only brand on the page.higgsfield website create --type website--type app— a product tightly integrated with Higgsfield: its users Sign in with Higgsfield and generate images/videos through the fnf SDK (the full auth + D1 contract applies). An app must look and feel like a Higgsfield product: UI built with Quanta (references/quanta-design.md) — and, for anything Quanta lacks, your own component built from Quanta primitives (never a third-party UI library) — starting from a standard app layout (references/app-layouts.md). Quanta and the app layouts are app-only — never applied to a--type websitebuild. The independent-brand rule and the wow pipeline (design-taste-frontend, boards, wow catalog) are the website path; apps never get a custom brand — Quanta is the brand.higgsfield website create --type app
What ships with it
20 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.
- references/app-cover.md 14 KB
- references/app-flow.md 22 KB
- references/app-layouts.md 6.2 KB
- references/asset-system.md 12 KB
- references/auth.md 11 KB
- references/containers.md 16 KB
- references/design-recipe.md 11 KB
- references/design-taste-frontend.md 86 KB
- references/fnf-react.md 9.7 KB
- references/fnf-sdk.md 25 KB
- references/image-to-code.md 6.4 KB
- references/quanta-design.md 31 KB
- references/reference-boards.md 6.5 KB
- references/review-rubric.md 5.2 KB
- references/runtime-and-infra.md 9.4 KB
- references/security.md 37 KB
- references/seo.md 36 KB
- references/website-flow.md 24 KB
- references/wow-catalog.md 6.3 KB
- references/wow-maker.md 21 KB
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 · 180 lines · 250 tokens per session scan C a6df452db4ed
higgsfield-websites is a skill published in the GitHub repository isaacsight/kernel (16 stars, last pushed 8d ago), licensed MIT. It adds 250 tokens to every session and 2,350 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker…
codegen-react
Scaffold and iterate on Vite + React applications.
frontend-architect
Frontend stack expert for Cloudflare deployment, shadcn/ui components, and internal tools architecture. Guides technology choices, deployment patterns, and design system integration.
website-builder
Build an approved Vite/React/Tailwind plan, collect assets, verify static output, deploy to GitHub Pages, and emit metadata. Use for implementing tasks.md. Don't use for design review, planning, backend services, or unapproved specs.
archestra-dev-frontend
Use when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
algolia-search-v2
Algolia Search Integration workflow skill. Use this skill when the user needs Expert patterns for Algolia search implementation, indexing and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.