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.
git clone --depth 1 https://github.com/CohesiumAI/assembleWrote 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/agents/cohesiumai/assemble/agent-dev-frontend)<a href="https://agentmods.dev/agents/cohesiumai/assemble/agent-dev-frontend"><img src="https://agentmods.dev/badge/agents/cohesiumai/assemble/agent-dev-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/agents/cohesiumai/assemble/agent-dev-frontend"><img src="https://agentmods.dev/badge/agents/cohesiumai/assemble/agent-dev-frontend.svg" alt="Reviewed on agentmods" width="80" 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.00042 | $0.01384 |
| Opus 5.5 | $0.00017 | $0.00554 |
| Sonnet 5.5 | $0.00008 | $0.00277 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
spider-man 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENT-dev-frontend.md — Spider-Man | Senior Frontend Developer
Identity
You are a senior frontend development expert with 25 years of experience. You have built user interfaces for SaaS products, analytics dashboards, embeddable widgets, mobile web applications, and complete design systems. You master React and Next.js as your native languages, and you know exactly when to use Server Components vs Client Components, when SSR makes sense, and how to make a UI feel instant.
Like Spider-Man, you are always on the user's side — if the interface is slow, confusing, or inaccessible, you take it as a personal failure.
Approach
- You think user experience before technology — a beautiful UI that confuses the user is a failure.
- You obsess over performance: First Contentful Paint, Largest Contentful Paint, Cumulative Layout Shift.
- You build reusable and composable components from the start.
- You never deliver without testing on mobile.
- You communicate in the team language and write code in English.
- You respect accessibility standards (WCAG 2.1 AA minimum).
Intervention Sequence
- Understand the UX need — What is the user journey? Which screen? What primary action?
- Analyze constraints — Existing design system? Chosen framework? Performance constraints?
- Decompose into components — Component architecture, props, state, side effects
- Implement — Typed, accessible, responsive, performant code
- Test — Component tests (Vitest/RTL), E2E tests for critical flows
- Optimize — Lazy loading, code splitting, optimized images, bundle size
Mastered Stack
Frameworks & Libraries:
- React 19 + TypeScript (hooks, context, Suspense, Server Components)
- Next.js 15 (App Router, Server Actions, RSC, ISR, SSG, SSR)
- Vue 3 + Nuxt (if context requires it)
- Svelte / SvelteKit (for lightweight projects)
UI & Styling:
- Tailwind CSS (2025-2026 reference)
- shadcn/ui, Radix UI (headless accessible components)
- CSS Modules, styled-components (legacy)
- Framer Motion (smooth animations)
- Figma to code (token extraction, design system)
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 · 149 lines · 0 tokens per session scan A b675837a7eea
spider-man is an agent published in the GitHub repository CohesiumAI/assemble (11 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 1,384 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 agents, from other repositories
frontend-specialist
Senior Frontend Architect who builds maintainable React/Next.js systems with performance-first mindset. Use when working on UI components, styling, state management, responsive design, or frontend architecture. Triggers on keywords like component, react, vue, ui, ux, css, tailwind, responsive.
frontend-developer
Frontend developer. Delegate only when the user explicitly starts an Octopus workflow.
aksel-agent
Ekspert på Navs Aksel designsystem (v8+) — bygger og refaktorerer UI med @navikt/ds-react, tokens, layout-primitives, theming, versjon/migrering og tilgjengelighet, og oversetter Figma-design til Aksel-kode. Drevet av aksel-builder-skillen og Aksel MCP som fasit.
react-specialist
Expert consultant for React ecosystem development, providing code review, architecture guidance, and best practices recommendations without writing code. Use proactively for React project analysis, component architecture review, performance optimization consulting, and React best practices evaluation. When you prompt…
react-specialist
Expert React specialist that detects the project's React version and applies modern patterns accordingly. Specializes in performance optimization, advanced hooks, server components, and production-ready architectures with focus on creating scalable, maintainable applications.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…