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 punkadillo/figma-code-composer --skill atomic-design-organismsgit clone --depth 1 https://github.com/punkadillo/figma-code-composerWrote 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/punkadillo/figma-code-composer/atomic-design-organisms)<a href="https://agentmods.dev/skills/punkadillo/figma-code-composer/atomic-design-organisms"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/atomic-design-organisms/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/punkadillo/figma-code-composer/atomic-design-organisms"><img src="https://agentmods.dev/badge/skills/punkadillo/figma-code-composer/atomic-design-organisms.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.00034 | $0.07562 |
| Opus 5.5 | $0.00014 | $0.03025 |
| Sonnet 5.5 | $0.00007 | $0.01512 |
| Haiku 4.5 | $0.00003 | $0.00756 |
Grade A, and why
atomic-design-organisms 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 — 1,278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atomic Design: Organisms
Master the creation of organisms - complex, distinct sections of an interface composed of molecules and atoms. Organisms represent standalone UI sections that could exist independently.
What Are Organisms?
Organisms are relatively complex UI components that form distinct sections of an interface. They are:
- Composed of molecules and atoms: May include both levels
- Standalone sections: Can exist independently on a page
- Context-aware: Often tied to specific business contexts
- Stateful: May manage significant internal state
- Reusable: Used across different templates and pages
Common Organism Types
Navigation Organisms
- Header (logo + navigation + user menu)
- Footer (links + social icons + legal)
- Sidebar (navigation + user info + actions)
- Breadcrumbs (full navigation path)
Content Organisms
- Product cards (image + details + actions)
- Comment sections (comments + reply forms)
- Article previews (title + excerpt + meta)
- User profiles (avatar + bio + stats)
Form Organisms
- Login forms (fields + actions + links)
- Registration forms (multi-step fields)
- Checkout forms (payment + shipping)
- Search with filters
Data Display Organisms
- Data tables (header + rows + pagination)
- Dashboards (stats + charts + actions)
- Timelines (events + connectors)
- Galleries (images + navigation)
Header Organism Example
Complete Implementation
// organisms/Header/Header.tsx
import React, { useState } from 'react';
import { Icon } from '@/components/atoms/Icon';
import { Button } from '@/components/atoms/Button';
import { Avatar } from '@/components/atoms/Avatar';
import { NavItem } from '@/components/molecules/NavItem';
import { SearchForm } from '@/components/molecules/SearchForm';
import styles from './Header.module.css';
export interface NavLink {
id: string;
label: string;
href: string;
icon?: string;
badge?: number;
}
export interface User {
id: string;
name: string;
email: string;
avatar?: string;
}
export interface HeaderProps {
/** Logo element or image */
logo: React.ReactNode;
/** Navigation links */
navigation: NavLink[];
/** Current active nav item */
activeNavId?: string;
/** Authenticated user */
user?: User | null;
/** Show search form */
showSearch?: boolean;
/** Search submit handler */
onSearch?: (query: string) => void;
/** Login click handler */
onLogin?: () => void;
/** Logout click handler */
onLogout?: () => void;
/** Profile click handler */
onProfileClick?: () => void;
}
export const Header: React.FC<HeaderProps> = ({
logo,
navigation,
activeNavId,
user,
showSearch = true,
onSearch,
onLogin,
onLogout,
onProfileClick,
}) => {
const [mobileMenuOpen, setMobileMenuOpen] = useState(false);
const [userMenuOpen, setUserMenuOpen] = useState(false);
return (
<header className={styles.header}>
<div className={styles.container}>
{/* Logo */}
<div className={styles.logo}>{logo}</div>
{/* Desktop Navigation */}
<nav className={styles.nav} aria-label="Main navigation">
<ul className={styles.navList}>
{navigation.map((item) => (
<li key={item.id}>
<NavItem
label={item.label}
href={item.href}
icon={item.icon}
badge={item.badge}
isActive={item.id === activeNavId}
/>
</li>
))}
</ul>
</nav>
{/* Search */}
{showSearch && onSearch && (
<div className={styles.search}>
<SearchForm
onSubmit={onSearch}
placeholder="Search..."
size="sm"
/>
</div>
)}
{/* User Actions */}
<div className={styles.actions}>
{user ? (
<div className={styles.userMenu}>
<button
className={styles.userButton}
onClick={() => setUserMenuOpen(!userMenuOpen)}
aria-expanded={userMenuOpen}
aria-haspopup="true"
>
<Avatar
src={user.avatar}
alt={user.name}
initials={user.name.slice(0, 2).toUpperCase()}
size="sm"
/>
<span className={styles.userName}>{user.name}</span>
<Icon name="chevron-down" size="xs" />
</button>
{userMenuOpen && (
<div className={styles.dropdown}>
<button onClick={onProfileClick}>
<Icon name="user" size="sm" />
Profile
</button>
<button onClick={onLogout}>
<Icon name="log-out" size="sm" />
Logout
</button>
</div>
)}
</div>
) : (
<Button variant="primary" size="sm" onClick={onLogin}>
Login
</Button>
)}
</div>
{/* Mobile Menu Toggle */}
<button
className={styles.mobileToggle}
onClick={() => setMobileMenuOpen(!mobileMenuOpen)}
aria-expanded={mobileMenuOpen}
aria-label="Toggle menu"
>
<Icon name={mobileMenuOpen ? 'x' : 'menu'} size="md" />
</button>
</div>
{/* Mobile Navigation */}
{mobileMenuOpen && (
<nav className={styles.mobileNav} aria-label="Mobile navigation">
<ul>
{navigation.map((item) => (
<li key={item.id}>
<NavItem
label={item.label}
href={item.href}
icon={item.icon}
badge={item.badge}
isActive={item.id === activeNavId}
onClick={() => setMobileMenuOpen(false)}
/>
</li>
))}
</ul>
</nav>
)}
</header>
);
};
Header.displayName = 'Header';
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 · 1,278 lines · 34 tokens per session scan A 918a6453a672
atomic-design-organisms is a skill published in the GitHub repository punkadillo/figma-code-composer (3 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 7,562 once invoked, about $0.0001 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-31.
Other skills, from other repositories
moai-design-tools
Design tool integration specialist covering Figma MCP, Pencil renderer, and Pencil-to-code export. Use when fetching design context from Figma, rendering Pencil designs, or exporting to React/Tailwind code.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
moai-domain-design-dna
Reverse-engineer a reference design — a screenshot, an image set, or a live URL — into a portable Design DNA JSON across three dimensions (measurable tokens, qualitative style, special-rendering effects), then generate a new self-contained artifact from that JSON. Carries the extraction rules (dominance-based colour…
figma-codegen
Generate framework-aware code from a Figma design. Reads the project's stack profile and emits code matching the existing framework (React/Vue/Svelte/Next/etc.) and styling (Tailwind/CSS/CSS-in-JS), reusing existing components and design tokens instead of regenerating from scratch. Triggers whenever the user wants a…
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
moai-domain-frontend
Frontend development specialist covering React 19, Next.js 16, Vue 3.5, and modern UI/UX patterns with component architecture. Use when building web UIs, implementing components, optimizing frontend performance, or integrating state management.