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/moasq/agentic-ship/clone-websitenpx skills add moasq/agentic-ship --skill clone-websitegit clone --depth 1 https://github.com/moasq/agentic-shipWhat 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.00071 | $0.02074 |
| Opus 5 | $0.00036 | $0.01037 |
| Sonnet 5 | $0.00014 | $0.00415 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
clone-website 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clone Website
Downstream contract: paths like
src/,docs/, andpublic/refer to the product workspace that adopts Agentic Ship, not this tool repo. Adapted from the MIT-licensedJCodesMore/ai-website-cloner-templateskill; provenance and the sync path live inskills.lock.json.
You are a foreman walking the job site. As you inspect each section of the target page you write a specification file with exact measured values, then build (or dispatch a builder for) exactly that section. Extraction and construction interleave; extraction is meticulous and leaves auditable artifacts. A builder that has to guess a color, a font size, or a padding value means extraction failed — go measure it.
0. Rights decide fidelity — settle this before extraction
AGENTS.md (Cloning rules) declares the boundary; this is the procedure:
- Owned-site clone. The user owns the target or holds rights to it (platform migration, lost source, their own older stack). Full fidelity is the job: real copy, real assets, exact composition. Confirm ownership in one question when it is not already stated; record the answer in the output plan.
- Reference rebuild — the default for anyone else's site. The pipeline runs
identically, but what ships is the site's system, re-voiced: layout, scale,
spacing, type hierarchy, palette structure, interaction models and motion feel
transfer; copy, brand assets, logos, photography, illustrations and trademarks do
not. Content is rewritten in the product's voice, assets are sourced independently
(
ui-system/references/asset-pipeline.md), fonts follow the license rules below, and at least a few deliberate composition divergences are made and recorded in the spec files. Extraction artifacts underdocs/are research and never ship in UI.
Never present a reference rebuild as pixel-identical to someone else's brand, and stop for the user if the request is to impersonate a real organization's site rather than to build their product's own.
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.
- 3d ago First seen · 152 lines · 71 tokens per session scan A a65d3acfd487
clone-website is a skill published in the GitHub repository moasq/agentic-ship (10 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 2,074 once invoked, about $0.0004 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…