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/simplify-julesnpx skills add jonathanmalkin/jules --skill simplify-julesgit clone --depth 1 https://github.com/jonathanmalkin/julesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jonathanmalkin/jules/simplify-jules)<a href="https://agentmods.dev/skills/jonathanmalkin/jules/simplify-jules"><img src="https://agentmods.dev/badge/skills/jonathanmalkin/jules/simplify-jules.svg" alt="Measured on agentmods" height="20"></a>What 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.01284 |
| Opus 5 | $0.00011 | $0.00642 |
| Sonnet 5 | $0.00004 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
simplify-jules 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 5d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/simplify-jules
On-demand config hygiene tool. Analyzes the full cold-start file bundle for waste, duplication, stale content, and consolidation opportunities. All proposals require [Your Name]'s approval — never auto-edit any file.
Phase 1 — INVENTORY
Read and count lines in every cold-start file:
~/.claude/CLAUDE.mdand all@-imported files it referencesActive-Work/CLAUDE.mdand all@-imported files it references- All
.claude/rules/*.mdfiles - All
@-tagged profile files (Profiles/*.md)
For each file, record: file path, line count.
Report:
Cold-Start Budget: X lines
Files scanned: N
Largest files: [top 5 by line count]
Phase 2 — SECTION ANALYSIS
For each file, read every section (heading or logical block) and classify it:
| Classification | Definition |
|---|---|
| ACTIONABLE | Directly changes agent behavior — keep as-is |
| DOCUMENTATION | Describes or explains but doesn't change behavior — propose move to Documents/ |
| REDUNDANT | Already said elsewhere — propose cut, cite exact duplicate (file:line) |
| VAGUE | Too abstract to change behavior — propose cut or rewrite |
Output one table per file:
### ~/.claude/CLAUDE.md
| Section | Lines | Classification | Notes |
|---------|-------|----------------|-------|
| User Preferences | 1-3 | DOCUMENTATION | Says "see project CLAUDE.md" |
...
Cite line numbers for every section.
Phase 3 — CROSS-FILE DEDUP
After reading all files, scan for:
- Duplicate instructions — same rule stated in multiple files. List both locations.
- Conflicting instructions — contradictory rules. Flag both locations, describe the conflict.
- Consolidation opportunities — related content spread across files that could merge without loss.
Format:
### Duplicates
- "Stage specific files for commits" — rules/safety.md:12 AND CLAUDE.md:47
### Conflicts
- "Use Opus for complex analysis" (CLAUDE.md:89) vs "Default to Sonnet" (rules/models.md:5) — unclear precedence
### Consolidation
- Agent delegation rules split across CLAUDE.md:82-95 and rules/request-routing.md:44-60 — could merge
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.
- 5d ago First seen · 168 lines · 22 tokens per session scan A f63f3bb28ca5
simplify-jules is a skill published in the GitHub repository jonathanmalkin/jules (65 stars, last pushed 3mo ago), licensed MIT. It adds 22 tokens to every session and 1,284 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…