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/formnpx skills add maxtechera/ship --skill formgit 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.00022 | $0.00575 |
| Opus 5 | $0.00011 | $0.00287 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
Grade A, and why
content-form 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 yesterday.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Form
Define form assets that capture leads without funnel friction.
Types
- Lead capture forms (top-of-funnel, minimal fields)
- Demo/consult booking forms
- Post-signup onboarding forms
- Feedback/NPS forms
- Objection and churn-intent forms
Inputs Required
- Funnel stage and conversion goal
- Offer and CTA context from landing page
- CRM/email destination (list, group, automation)
- Tracking requirements (GA4 events, UTMs)
Required Outputs
- Field schema: required/optional flags, field types, order
- Microcopy: labels, placeholders, helper text, error messages, submit button text
- Submit behavior: redirect URL or inline confirmation
- Event tracking contract:
view,start,submit,success,dropoff - Routing rules: CRM list, email automation trigger, notification webhook
Conversion Rules
- Top-of-funnel forms: email only (or email + first name max)
- Mid-funnel forms: email + 1-2 qualifying fields
- Demo/high-intent forms: email + company + use case
- Never ask for phone without explicit reason
- Submit button copy = outcome ("Get Free Guide", not "Submit")
Event Tracking Contract
form_view → user sees the form
form_start → user focuses first field
form_submit → user clicks submit
form_success → server confirms submission
form_dropoff → user abandons without submitting
All events include: form_id, page_url, utm_source, utm_medium, utm_campaign
Integration Wiring
- Email capture → email provider group/list (with tags)
- Lead magnet delivery → automation trigger fires on
form_success - CRM sync → contact created/updated with source attribution
- Notification → internal webhook to Slack/Telegram (optional)
Test Protocol
Before going live:
- Submit test entry → confirm email received
- Check UTM attribution passed through
- Verify GA4
form_successevent fires - Confirm automation trigger fires
- Log test result with screenshot
Done Criteria
- Field schema defined with required/optional
- Microcopy written (labels, placeholders, errors, submit)
- Event tracking contract documented
- Routing rules specified (list, automation, CRM)
- End-to-end test protocol defined
- Consent language included where required
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.
- yesterday First seen · 80 lines · 22 tokens per session scan A 19c6de59ba8e
content-form is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 575 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…