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 skills add AlexK020908/infra-designer --skill scheduler-schedulegit clone --depth 1 https://github.com/AlexK020908/infra-designerWrote 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/alexk020908/infra-designer/scheduler-schedule)<a href="https://agentmods.dev/skills/alexk020908/infra-designer/scheduler-schedule"><img src="https://agentmods.dev/badge/skills/alexk020908/infra-designer/scheduler-schedule/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/alexk020908/infra-designer/scheduler-schedule"><img src="https://agentmods.dev/badge/skills/alexk020908/infra-designer/scheduler-schedule.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
scheduler-schedule 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 12d 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
aws.scheduler.schedule
Managed cron (EventBridge Scheduler): fires on a schedule and triggers exactly ONE target — an aws.lambda.function or an aws.sqs.queue. Config knobs: scheduleExpression (default rate(1 day)), timezone (default UTC).
Scheduling
- Expressions:
rate(5 minutes)/rate(1 day)for intervals,cron(0 9 * * ? *)for wall-clock times (interpreted intimezone— daylight saving handled). - One schedule node per job. A schedule has exactly one target; multiple recurring jobs mean multiple schedule nodes.
Choosing a target
- Heavy or fan-out work: target the job QUEUE (schedule → sqs → workers), reusing the design's retry/DLQ machinery. Target a Lambda directly only for light, self-contained ticks.
- Targets must be idempotent: delivery is at-least-once and a missed window may fire late — the run must be safe to repeat (see long-running-tasks.md for job mechanics).
- This replaces the old workaround of an always-on ECS service running a timer loop — never propose that again; a schedule node costs ~nothing.
Edges & IAM
- Edge kind: schedule → target is data. The schedule's IAM role (emitted automatically) carries the invoke/send permission.
What ships with it
3 files 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.
- 12d ago First seen · 16 lines · 0 tokens per session scan A 235f0cc286f6
scheduler-schedule is a skill published in the GitHub repository AlexK020908/infra-designer (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 tokens. 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
terraform-skill
Use when working with Terraform or OpenTofu - creating modules, writing tests (native test framework, Terratest), setting up CI/CD pipelines, reviewing configurations, choosing between testing approaches, debugging state issues, implementing security scanning (trivy, checkov), or making infrastructure-as-code…
terraform-cli-setup
A setup guide for installing and initializing Terraform, a tool for managing infrastructure from configuration files. It also covers basic provider downloads and mirror settings, but not cloud-provider credentials.
alicloud_cli
A Chinese-language reference for the Alibaba Cloud command-line tool, which lets developers manage Alibaba Cloud services from a terminal. It uses an offline copy of the documentation as its main source.
deploy
A deployment workflow for putting Rails applications online using Railway, a hosting service.
oss-upload
Upload local files to Tencent COS (oss.1024code.com CDN) using coscli. Use when user wants to upload a file to CDN/OSS, or deploy static assets.
webflow-cli:cloud
Create, build, and deploy Webflow Cloud apps from the CLI (site-attached or project apps), and manage existing ones — apps, domains, environments, deployments, build/runtime logs, and environment variables including secrets. Use when initializing or deploying a Cloud app, importing an existing GitHub repository…