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 agentmods add skills/beefiker/superloopy/superloopy-clonenpx skills add beefiker/superloopy --skill superloopy-clonegit clone --depth 1 https://github.com/beefiker/superloopyWrote 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/beefiker/superloopy/superloopy-clone)<a href="https://agentmods.dev/skills/beefiker/superloopy/superloopy-clone"><img src="https://agentmods.dev/badge/skills/beefiker/superloopy/superloopy-clone.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 | $0.00113 | $0.04422 |
| Opus 5 | $0.00056 | $0.02211 |
| Sonnet 5 | $0.00023 | $0.00884 |
| Haiku 4.5 | $0.00011 | $0.00442 |
Grade A, and why
superloopy-clone 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 4d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superloopy Clone
Reverse-engineer a target URL into a working local implementation with audit artifacts. Use this only for authorized cloning, migration, learning, or recovery work. Do not help with phishing, deceptive impersonation, credential capture, or evading a site's terms.
When multiple URLs are provided, process each host independently. Keep every site's research, screenshots, assets, and evidence isolated under paths like docs/research/<hostname>/, docs/design-references/<hostname>/, and .superloopy/evidence/website-clone/<hostname>/.
This is not "inspect once, then redraw." Act as the foreman: inspect one section, write the exact spec, dispatch or build that bounded slice, then keep extracting the next section while builders run. A hard section is where extraction gets stricter, not where approximation becomes acceptable.
Reference Example
Transferloom.com is a reference result for this workflow: superloopy-clone reproduced the page locally and passed desktop/mobile browser validation with preserved sticky navigation, animated hero, app preview sections, comparison table, security panel, sister app banner, footer, local assets, and a Superloopy evidence trail.
Use that bar for completion claims. A clone is successful only when it has this shape of evidence: source screenshots, research notes, component specs, downloaded assets, local browser screenshots, validation output, visual QA notes, and a final evidence artifact.
Superloopy Contract
- Create or reuse a Superloopy plan. Use an evidence root like
.superloopy/evidence/website-clone/<hostname>/. - Preserve extraction artifacts: screenshots, topology, behavior notes, component specs, asset inventory, validation output, and visual QA notes.
- Record final proof with
SUPERLOOPY_EVIDENCE: <path-under-active-evidence-root>when a worker is involved, orsuperloopy loop evidencewhen recording from the parent. - Do not add dependencies without asking. If a clone needs a package for parity, explain why and get approval first.
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.
- 4d ago First seen · 306 lines · 113 tokens per session scan A 87ab98550ed0
superloopy-clone is a skill published in the GitHub repository beefiker/superloopy (108 stars, last pushed 9d ago), licensed MIT. It adds 113 tokens to every session and 4,422 once invoked, about $0.0006 per session on Opus 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
maestro-design
Use when creating UI components, pages, design systems, or converting Figma/mockups to code. Covers Tailwind + shadcn/ui + Radix primitives, design tokens, responsive, a11y (WCAG 2.2), motion, and Figma→code workflow. Use for scaffolding a design system or generating production-ready UI. Triggers: figma, tailwind…
compose-creative-ui
기존 프론트엔드의 정체성과 디자인 시스템을 보존하면서 shadcn/ui registry, Magic UI, Aceternity UI, React Bits, Radix, Base UI, React Aria, Ark UI 등 호환 가능한 컴포넌트·시각 효과 도구를 선별해 화면 구성 자체를 구현·검증한다. 사용자가 랜딩 페이지, hero, 배경, 카드, bento, 텍스트 효과나 밋밋한 화면의 시각적 조합 개선을 요청할 때 사용한다. 시간·공간 변화는 implement-ui-motion을, 키보드·포커스·제스처·상태 동작은 implement-ui-interaction을…
implement-ui-motion
기존 프론트엔드에서 시간·공간 변화의 표현 자체가 주된 결과물인 모션과 마이크로인터랙션을 설계하고 CSS, Web Animations API, View Transition API, Anime.js, Motion 또는 GSAP 중 가장 단순한 기술로 구현·검증한다. 사용자가 애니메이션 적용, 버튼·카드의 시각 피드백, 페이지·레이아웃 전환, 스크롤·타임라인·SVG 모션, 라이브러리 선택, reduced-motion 또는 모션 성능 수정을 요청할 때 사용한다. 키보드·포커스·터치·제스처 입력은 implement-ui-interaction을, 요청·작업의 비동기 상태…
build-design-system
기존 코드베이스의 디자인 토큰, 테마, 컴포넌트 API, variant·state, 문서화와 회귀 검증을 하나의 시스템으로 설계·구현·마이그레이션한다. 사용자가 디자인 시스템이나 컴포넌트 라이브러리 구축·정리, CSS 변수·DTCG 토큰·Style Dictionary 파이프라인, Storybook 상태 문서, 다크 모드·브랜드 테마, 중복 컴포넌트 통합 또는 점진적 마이그레이션을 요청할 때 사용한다. 한 화면의 시각적 조합만 개선하면 compose-creative-ui를, 구현 없이 원칙이나 명세만 필요하면 uiux-advisor를, 기존 시스템 감사만 필요하면…
retheme
Systematically apply an approved design lane (LANE.md) to a React + Tailwind site — tokens first, then section-by-section, with build + screenshot verification after every pass. Use when the user says "retheme", "apply the lane", "make it match the design", or after /unslop:interview produced an approved LANE.md.
audit
Score an existing React + Tailwind site against the anti-slop checklist and produce DESIGN-AUDIT.md with evidence. Use when the user says their site "looks AI-generated", "looks generic", "feels off", asks "why is my site ugly", or wants a design audit/score before improving it. Read-only — never edits source.