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 instructions/yuuqq/jules-dispatch/claude-mdgit clone --depth 1 https://github.com/Yuuqq/jules-dispatchWrote 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/instructions/yuuqq/jules-dispatch/claude-md)<a href="https://agentmods.dev/instructions/yuuqq/jules-dispatch/claude-md"><img src="https://agentmods.dev/badge/instructions/yuuqq/jules-dispatch/claude-md.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.00389 | $0.00389 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
jules-dispatch CLAUDE.md 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 4d 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.
What it actually says
jules-dispatch — Project Guide
Project
CLI + MCP server for batch-dispatching coding tasks to Google Jules in parallel. Published on npm as @yuuqq/jules-dispatch (bin: jules-dispatch). TypeScript, Node 20+, ESM. Note: the unscoped npm name jules-dispatch is taken by an unrelated package — always use the scoped name in install instructions.
GSD Workflow
This project uses GSD (Get Shit Done) for structured development.
- Planning directory:
.planning/ - Project context:
.planning/PROJECT.md - Requirements:
.planning/REQUIREMENTS.md(18 v1 requirements) - Roadmap:
.planning/ROADMAP.md(10 phases) - Config:
.planning/config.json(YOLO, Fine, Parallel, Quality)
Commands
npm run build # TypeScript → dist/
npm run dev # Run CLI with tsx
npm run test # vitest
npm run typecheck # tsc --noEmit
Key Conventions
- ESM only —
"type": "module",.jsextension in imports - Dual output — every user-facing op calls
emit(textFn, jsonObj)(output.ts) - Exit codes — 0 OK, 1 generic, 2 auth, 3 validation, 4 partial, 5 timeout
- Thin client — JulesClient is pure HTTP; orchestration in dispatcher/collector
- Immutability — create new objects, never mutate
Current Milestone
Incremental optimization: MCP tool consolidation (12→8), CLI progress visibility, data foundation hardening.
Phase 1 is next: /gsd-plan-phase 1 to start.
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.
- 4d ago First seen · 39 lines · 389 tokens per session scan A 4b78d090060f
jules-dispatch CLAUDE.md is an instructions file published in the GitHub repository Yuuqq/jules-dispatch (4 stars, last pushed 21d ago), licensed MIT. It adds 389 tokens to every session, about $0.0019 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 instructions, from other repositories
seektty AGENTS.md
AGENTS.md instructions for Hilbert-beinghappy/seektty: This repository ships one out-of-tree DeepSeek Harness Bundle. Harness remains the only owner of Agent, Session, model, settings, permissions, Profile, plugin, and persistence state.
amp-acp AGENTS.md
Instructions for tao12345666333/amp-acp, covering agents.md, commands, architecture and code style.
roamcode AGENTS.md
AGENTS.md instructions for burakgon/roamcode, covering repository instructions for coding agents, public-repository safety, stable release and ota contract, releasing a stable version and ota changes.
dev-workspace AGENTS.md
Instructions for iwe-org/dev-workspace, covering agent operating manual, start of every session, the operating loop, conventions and iwe basics.
ob-1 AGENTS.md
Instructions for Overbrilliant/ob-1, covering agents.md, project index, stack, commands and key files.
kumo-coding-agent AGENTS.md
Instructions for kumo-ai/kumo-coding-agent: All instructions, routing tables, and rules are in CLAUDE.md. Read that file as the entry point for this agent.