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/creative-int/sagu-plugins/sagu-dispatchnpx skills add creative-int/sagu-plugins --skill sagu-dispatchgit clone --depth 1 https://github.com/creative-int/sagu-pluginsWrote 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/creative-int/sagu-plugins/sagu-dispatch)<a href="https://agentmods.dev/skills/creative-int/sagu-plugins/sagu-dispatch"><img src="https://agentmods.dev/badge/skills/creative-int/sagu-plugins/sagu-dispatch.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.00075 | $0.00788 |
| Opus 5 | $0.00037 | $0.00394 |
| Sonnet 5 | $0.00015 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
sagu-dispatch 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sagu — dispatch radars and pings
Sagu is an AI-powered monitoring platform. A radar tracks a topic you care about, and Sagu generates periodic intelligence reports called pings. This skill connects an agent to Sagu's radar and ping tools over MCP.
Connect to the Sagu MCP server at https://sagu-mcp.luke-nittmann.workers.dev/mcp,
or run the local stdio server with npx -y @sagu/mcp and a RADAR_API_KEY.
Use when
- The user asks about a radar, topic, or ongoing monitoring subject.
- You need recent intelligence, sources, or citations about a tracked topic.
- You want to export a ping as an agent-ready context packet for another workflow.
- The user asks to refresh a radar, run a new intelligence pass, or check ping status.
- The user asks a follow-up question inside a radar's thread.
Don't use when
- The answer is fully available in the current workspace files.
- The user asks about private data outside their authenticated Sagu account.
- You need to create or share artifacts — use
sagu-artifactfor that.
MCP tools
radar_list_radars(sagu.radars) — list all radars; filter by status and limit.radar_get_radar(sagu.radars) — get one radar's knowledge graph, source stats, and learning metrics.radar_search(sagu.radars) — search radars by topic or description.radar_get_pings(sagu.pings) — get recent pings for a radar.radar_get_ping(sagu.pings) — get one ping by ID with full content.radar_get_ping_packet(sagu.pings) — export a ping as an agent-facing context packet (JSON or Markdown) with citations, source cards, why-included notes, and stable source IDs.radar_refresh(sagu.pings) — trigger a new ping generation for a radar.radar_thread_ask(sagu.pings) — ask a question in a radar's thread.radar_get_info(sagu.meta) — get account context and radar count.
How to dispatch well
- Discover. Call
radar_list_radarsorradar_searchto find the relevant radar. - Read. Use
radar_get_radarfor the radar overview, thenradar_get_pingsorradar_get_pingfor the intelligence. - Export. When the ping is going into another agent or workflow, use
radar_get_ping_packetwithformat: "json"to preserve citations and stable IDs. Useformat: "markdown"for direct reading. - Refresh. If the latest ping is stale, call
radar_refreshand tell the user the run is queued. Pollradar_get_pingsfor the new ping. - Cite. Always carry Sagu citations forward; don't collapse sourced claims into unsourced summaries.
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 · 64 lines · 75 tokens per session scan A a114ee0316db
sagu-dispatch is a skill published in the GitHub repository creative-int/sagu-plugins (0 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 788 once invoked, about $0.0004 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…