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/talentnpx skills add maxtechera/ship --skill talentgit 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.00019 | $0.00536 |
| Opus 5 | $0.00010 | $0.00268 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
content-talent 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Talent
Support on-camera recording sessions. Prepare everything before, assist during, and process after.
Handoff Pack (Required Before Recording)
A complete handoff pack contains:
- Final script — reviewed, camera directions included
- Storyboard — shot-by-shot with visual descriptions
- Recording brief — setup, props, slides needed
- B-roll list — what supplementary footage to capture
- Teleprompter-ready text — large font, natural pacing, no jargon
Script Format for Talent
[SECTION: Hook — 0-3 seconds]
[LOOK AT CAMERA]
"[Opening line — bold, specific]"
[TEXT OVERLAY: "key stat or phrase"]
[SECTION: Problem — 3-10 seconds]
[SHOW SCREEN]
"[Problem description with specific detail]"
[SECTION: Solution — 10-45 seconds]
[ALTERNATE: camera + screen]
"[Step-by-step or narrative]"
[B-ROLL: screen recording of tool]
[SECTION: CTA — last 3 seconds]
[LOOK AT CAMERA]
"[Direct ask — follow, comment, click link]"
Teleprompter Guidelines
- Large font size for arm's-length reading
- Natural pacing — write like you speak, not like you write
- Mark pauses with
[pause] - Mark emphasis with CAPS
- Keep lines short — one idea per line
Post-Recording Processing
After recording session:
- Transcription — generate transcript from audio
- Caption file — SRT format for accessibility and text overlays
- Cut list — note timestamps of usable takes
- B-roll slots — mark where b-roll goes in the edit
- Thumbnail frames — identify best freeze-frames
Recording Session Rules
- No personal data visible on screen
- Clean desktop and relevant tabs only
- Test audio before rolling
- Capture 3-second silence before and after each take
- Record at least 2 takes for every section
Done Criteria
- Final script reviewed and camera-direction annotated
- Storyboard attached
- Teleprompter-ready version prepared
- B-roll list created before session
- Post-recording: transcript + caption file + cut list
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 · 77 lines · 19 tokens per session scan A e52d2f7a6915
content-talent is a skill published in the GitHub repository maxtechera/ship (2 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 536 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…