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/maxtechera/ship/pagenpx skills add maxtechera/ship --skill pagegit clone --depth 1 https://github.com/maxtechera/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.00024 | $0.00555 |
| Opus 5 | $0.00012 | $0.00278 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
content-page 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 2d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Page
Build page-level assets with problem-first structure and deployment-ready outputs.
Types
- Landing pages (cold traffic → email capture / trial)
- Pricing pages (feature comparison, toggle, tier CTAs)
- Competitor comparison pages
- FAQ / objection handling pages
- Thank-you and post-signup pages
Inputs Required
- Product brief and ICP
- Offer strategy (headline, value prop, guarantee)
- VoC quotes for social proof
- Channel intent (cold social / search / referral)
Required Outputs
- Page copy by section (hero, proof strip, value props, objections, CTA)
- Conversion intent map (primary + secondary CTA)
- SEO essentials (title, meta description, schema notes)
- Mobile-first layout notes and asset slots
- UTM and event tracking requirements
GTM Rules
- Problem-first headline — pain before feature claims
- Hero uses VoC language — ≥1 near-verbatim pain phrase in H1 or sub-headline
- One dominant CTA per page — no competing conversion actions
- Objection handling visible above final CTA — don't bury it in FAQ
- Copy humanized — no AI cadence; reads like a founder wrote it
Page Section Template
HERO
H1: [Pain phrase from VoC]
Sub: [Outcome promise + mechanism]
CTA: [Single action button]
Social proof strip: [logos / review count / metric]
PROBLEM FRAME
"If you're [persona], you probably [pain]..."
3 bullets of specific pain evidence
VALUE PROPS (3-4)
Icon + H3 + 2 sentences each
Anchor to ICP pain, not generic features
PROOF
Testimonial (verbatim, attributed)
Metric or case study
OBJECTION HANDLING
3-5 most common objections with direct responses
(Source from ICP research — not invented)
FINAL CTA
Restate outcome promise
Button + micro-copy (risk reversal)
FOOTER
FAQ (3-5 questions)
Done Criteria
- Hero uses VoC language
- Single dominant CTA
- Objection handling section present
- Copy humanized (no AI phrases)
- Mobile layout notes included
- UTM + event tracking specified
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.
- 2d ago First seen · 85 lines · 24 tokens per session scan A 990e676a750c
content-page is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 555 once invoked, about $0.0001 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…