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/agentry-ai/agentry/automationnpx skills add agentry-ai/agentry --skill automationgit clone --depth 1 https://github.com/agentry-ai/agentryWrote 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/agentry-ai/agentry/automation)<a href="https://agentmods.dev/skills/agentry-ai/agentry/automation"><img src="https://agentmods.dev/badge/skills/agentry-ai/agentry/automation.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.00000 | $0.01583 |
| Opus 5 | $0.00000 | $0.00792 |
| Sonnet 5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
automation 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Automation (scheduled jobs + webhooks, with a built-in control panel)
Use when the user says something like "build an automation", "run this on a schedule", "every morning / hourly / cron", "a worker that polls X", "handle a Stripe/GitHub/Slack webhook", "do something when an event comes in". Read this whole page before scaffolding.
The one idea
An automation is a normal kind: nextjs app (one project, one port —
CONTRACT.md still holds) that uses the baked @agentry/automation
package. You do NOT build a bespoke daemon, a cron container, or your own
logs UI. You get three things for free:
- Schedules that run in-process on a cron expression.
- Webhooks served as Next route handlers, with signature verification.
- A control panel at
/_agentry— run history, next-fire times, webhook payloads, "Run now", and "Replay" — fully templated. Don't rebuild it; it renders itself from the run store.
The sandbox is a running computer, so the scheduler is just a cron living in the app process. No external scheduler, no separate service.
Scaffold
project_create kind=automation does the scaffolding — it copies the
baked @agentry/automation template (scheduler + webhook router + control
panel) into your project. Then:
cd /workspace/projects/<name>
npm install # @agentry/automation + the DB drivers resolve here
Then project_start. Iterate with edits + project_logs; the control
panel at /_agentry is your observability (it's the automation's "Open it").
(Do NOT use kind: python-script for a scheduled/webhook job — it has no
schedule primitive and no UI. kind: automation is the one.)
What's in the template, and the only files you normally touch:
automations/jobs.ts— your schedules (defineSchedule)automations/hooks.ts— your webhooks (withWebhook)- everything else (instrumentation, control panel, store, next.config) is
plumbing — leave it. In particular do not edit
next.config.mjs:output: 'standalone', the instrumentation hook, and the DB-driver externals are load-bearing. Removing any of them silently stops the cron from firing or breaks the build.
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 · 143 lines · 0 tokens per session scan A 33c7c0359682
automation is a skill published in the GitHub repository agentry-ai/agentry (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,583 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
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.
x-scorecard
OpenSSF Scorecard for assessing open source project security. Check security best practices and compliance. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.