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/jonathanmalkin/jules/writenpx skills add jonathanmalkin/jules --skill writegit clone --depth 1 https://github.com/jonathanmalkin/julesWhat 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.00052 | $0.06687 |
| Opus 5 | $0.00026 | $0.03343 |
| Sonnet 5 | $0.00010 | $0.01337 |
| Haiku 4.5 | $0.00005 | $0.00669 |
Grade A, and why
write 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 — 683 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@Profiles/Voice-Samples-Raw.md
Write
Single-invocation pipeline that takes a topic and produces published content across platforms, with the website as the primary canvas.
Arrives from: Direct invocation or chained from /think when content creation is identified.
Supporting references:
@references/content-packet-schema.md@references/voice-scorecard.md@references/faq-reply-loop.md@references/platform-account-routing.md
Anti-Fabrication Guard
Before any platform-specific drafting: verify every factual claim in the draft is either (a) from [Your Name]'s stated source material, (b) from the article spec / creative brief, or (c) flagged with [VERIFY: ...]. Do not invent statistics, quotes, personal anecdotes, or specific claims. Use [PLACEHOLDER: personal story about X] for narrative elements [Your Name] should fill in.
Two Flow Shapes
| Shape | Stages | When |
|---|---|---|
| Business only | 1 → 2 → 3 → 4 → 8 | High-level concepts, outcomes, impacts. Most posts. |
| Business + Technical | 1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 | When the topic warrants deep technical detail (code, implementation). |
Stage Overview
| Stage | What | Who | Notes |
|---|---|---|---|
| 1. Seed + Source Material | Capture topic, stories, context | Jules + [Your Name] | ~5 min |
| 2. Decision Sprint + Creative Brief | Structured decisions, reviewable brief | [Your Name] (Jules facilitates) | 5-30 min |
| 3. Write + Edit + Publish Website (Business) | Draft, review panel, iterate, publish | Jules + [Your Name] | Variable |
| 4. LinkedIn + X (Business) | Adapt, iterate, publish. Decision point. | Jules + [Your Name] | Variable |
| 5. Write + Edit + Publish Website (Technical) | Expand with technical depth, publish | Jules + [Your Name] | OPTIONAL |
| 6. Reddit | Adapt technical article for Reddit, publish | Jules + [Your Name] | OPTIONAL |
| 7. LinkedIn + X (Technical) | Technical adaptations with Reddit link | Jules + [Your Name] | OPTIONAL |
| 8. Track | Update published records, URLs, and content state | Jules (auto) | ~1 min |
What ships with it
6 files 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.
- 2d ago First seen · 683 lines · 52 tokens per session scan A f4b8906fe07c
write is a skill published in the GitHub repository jonathanmalkin/jules (63 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 6,687 once invoked, about $0.0003 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
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…