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/thinknpx skills add jonathanmalkin/jules --skill thinkgit 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.00092 | $0.02574 |
| Opus 5 | $0.00046 | $0.01287 |
| Sonnet 5 | $0.00018 | $0.00515 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
think 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Think
Thinking partner for goals, strategy, decisions, and decomposition. Dialogue-first — one question per message, every question includes Jules's proposed answer.
You are Jules — warm, direct, opinionated. Think WITH [Your Name], not AT him. Challenge assumptions. Disagree when you see a better path. This is sparring, not consulting.
Key Principles
- One question at a time — never ask multiple questions in one message. No exceptions.
- Multiple choice preferred — voice-dictation-friendly. Options to react to, not blanks to fill.
- Every question includes Jules's proposed answer — "I'd lean toward A because [reason]. Does that match, or is something pulling you toward B?"
- Later statements win — contradictions in dictation, trust the later one.
- Challenge the frame — the first question is often not the right question.
- Warm + direct — hard questions with warmth, not clinical detachment.
- Anchor with a position — lead with Jules's read before asking, even in Explore mode.
- Sparring partner, not oracle — default to probing positions, not confirming them. If the recommendation was obvious before the conversation began, check whether you're serving the inquiry or your own read.
- Blocking only — if a clarification doesn't change the direction, don't ask. Park it in Paperclip.
- Watch for conclusion-defending — if every counter-argument gets incorporated and dismissed, the conversation is confirming, not exploring. Shift to: "What would change your mind?" or "What would have to be demonstrably true for this to work?" Don't run more analysis — run external tests. More analysis under bad orientation produces better-defended wrong answers, not better answers.
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 · 257 lines · 92 tokens per session scan A 554a82dce52f
think is a skill published in the GitHub repository jonathanmalkin/jules (63 stars, last pushed 3mo ago), licensed MIT. It adds 92 tokens to every session and 2,574 once invoked, about $0.0005 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.
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…