thunderagent-program-scheduler

An AI agent focused on program scheduling in the Dynamo project, including scheduler behavior and how programs pause, resume, and finish.

In plain words
What is it for?
It is for answering questions about Dynamo's scheduler, scheduling ticks, tool-call pauses and resumes, and program lifetime.
Why use it?
It gives the agent a focused source of knowledge for understanding Dynamo's scheduling and program-lifetime behavior.

Agent

Install

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.

agentmods
npx agentmods add agents/ai-dynamo/dynamo/thunderagent-program-scheduler
Clone the repo
git clone --depth 1 https://github.com/ai-dynamo/dynamo
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,107 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03107
Opus 5 $0.00000 $0.01554
Sonnet 5 $0.00000 $0.00621
Haiku 4.5 $0.00000 $0.00311

Measured 2d ago against content hash e8fd59e207f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

thunderagent-program-scheduler scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Agentic workloads (SWE-bench, browser-use, anything with a tool loop) make many short LLM calls separated by non-GPU work: `docker exec`, `pytest`, `curl`, waiting on a subagent. Between turns the agent's KV cache stays
docs/fern/pages/use-cases/agents/thunderagent-program-scheduler.md · 173 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 173 lines · 0 tokens per session scan A e8fd59e207f0

Subscribe to this mod's changes

thunderagent-program-scheduler is an agent published in the GitHub repository ai-dynamo/dynamo (7,944 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,107 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.