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 SII-Holos/synergy --skill develop-frontendgit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/develop-frontend)<a href="https://agentmods.dev/skills/sii-holos/synergy/develop-frontend"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/develop-frontend/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/sii-holos/synergy/develop-frontend"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/develop-frontend.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.00061 | $0.01697 |
| Opus 5.5 | $0.00024 | $0.00679 |
| Sonnet 5.5 | $0.00012 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
develop-frontend 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 yesterday.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop the Frontend
Preserve domain state and generated API ownership, public theme tokens, localization, real provider lifetimes and the current product contract. Use the verification table before choosing expensive checks. Read only references for the affected domain.
Read the Contracts
- Read
apps/web/AGENTS.mdand Web product contract. - Read Frontend data sync for contexts, snapshots, events, streaming, composer intent, or loaded buckets.
- Read Browser runtime for Browser UI or Desktop/Web presentation changes.
- Load
change-server-apiwhen the UI needs a new or changed server contract; loadadd-toolfor tool-card presentation.
Verify
Start with bun run verify plan. During iteration run the narrow component, model or context test; before publication use bun run verify local --test apps/web/test/<domain>/<file>.test.ts with all relevant tests explicitly selected. The entry point uses canonical coverage executors and static gates; it leaves complete package thresholds and platform acceptance to CI.
| Change | Additional local evidence |
|---|---|
| New source or test fixture | Fresh focused LCOV includes each new measurable source; read browser fixtures for real layout, virtualization and provider ownership. |
| Coverage policy, instrumentation, removed coverage | bun run verify coverage --package apps/web (or the actual owner). |
| Bootstrap, browser capabilities, bundler or package exports | Web production build, browser crypto contract and private HTTP smoke; verify local runs these for its known entry paths. Inspect the plan for other affected boundaries. |
| Copy, translations or locale formatting | Extract catalogs and run localization:check; verify cold start, switching, errors and lazy catalogs as described in presentation. |
| Visible interaction or layout | Inspect changed states, themes, focus and narrow geometry in one isolated runtime. |
| Native Browser, window chrome, protocol or Electron | Exercise the actual Desktop boundary using its owning skill. |
What ships with it
7 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.
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.
- yesterday Changed · +2 lines 613a699410b9
- 5d ago Changed 67a1e9195ed5
- 6d ago Changed · +6 lines bf23636e29a3
- 7d ago Changed · +2 lines a663df7d12e9
- 9d ago Changed · -357 lines 81aad5dd9e85
- 10d ago Changed · +6 lines e807bd4d7781
- 11d ago Changed · +26 lines a220551ecedb
- 13d ago Changed · +32 lines 936718a73755
- 14d ago Changed · +36 lines 90f7c139975d
- 15d ago First seen · 367 lines · 61 tokens per session scan A 5f8a500344b1
develop-frontend is a skill published in the GitHub repository SII-Holos/synergy (386 stars, last pushed today), licensed MIT. It adds 61 tokens to every session and 1,697 once invoked, about $0.0002 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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…