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 aeonfun/aeon --skill deploy-watchergit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/deploy-watcher)<a href="https://agentmods.dev/skills/aeonfun/aeon/deploy-watcher"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/deploy-watcher/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/aeonfun/aeon/deploy-watcher"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/deploy-watcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 19 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 38 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.01274 |
| Opus 5.5 | $0.00000 | $0.00510 |
| Sonnet 5.5 | $0.00000 | $0.00255 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
[REPLACE: SKILL_NAME] 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 1mo 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.
curl -sf -H "Authorization: Bearer $VERCEL_TOKEN" "$URL" > .vercel-deploys.json || \ Copies of this mod
1 near-identical copy found in the catalogue:
- deploy-watcher — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Optional. Override the Vercel project slug. If empty, watches
[REPLACE: VERCEL_PROJECT].
Today is ${today}. Watch Vercel deployments for [REPLACE: VERCEL_PROJECT] and alert on [REPLACE: ALERT_ON] within the last [REPLACE: LOOKBACK_HOURS] hours.
Required secrets
VERCEL_TOKEN— personal access token from https://vercel.com/account/tokens. Read scope is enough.- (optional)
VERCEL_TEAM_ID— if the project lives under a team, set this so the API queries the right scope.
If either secret is missing, log DEPLOY_WATCH_NO_TOKEN and exit cleanly — never abort the workflow.
Steps
-
Resolve scope:
PROJECT="${var:-[REPLACE: VERCEL_PROJECT]}" SCOPE_QS="" if [ -n "${VERCEL_TEAM_ID:-}" ]; then SCOPE_QS="&teamId=$VERCEL_TEAM_ID" fi -
Fetch recent deploys — Vercel API v6 lists deployments for a project:
SINCE_MS=$(( $(date -u +%s) * 1000 - [REPLACE: LOOKBACK_HOURS] * 3600 * 1000 )) URL="https://api.vercel.com/v6/deployments?projectId=$PROJECT&since=$SINCE_MS$SCOPE_QS&limit=20" curl -sf -H "Authorization: Bearer $VERCEL_TOKEN" "$URL" > .vercel-deploys.json || \ echo "DEPLOY_WATCH_FETCH_FAIL: $?"Make every Vercel call in-run with
./secretcurl(write the key as{VERCEL_TOKEN}— a bare$VERCEL_TOKENon the line is refused by the Bash permission layer). Read-only status checks and any irreversible action (e.g. triggering a deploy) both run in-run — the irreversible one as the skill's final, fail-closed action. Never defer a read. -
Parse and classify — for each deploy, capture:
uid,state(READY / ERROR / CANCELED / BUILDING / QUEUED),url,target(production / preview),creator,createdAt,meta.githubCommitMessage. -
Apply the alert filter —
[REPLACE: ALERT_ON]is one of:production-failures→ alert whentarget=productionANDstate in {ERROR, CANCELED}.any-failures→ alert on anystate in {ERROR, CANCELED}.slow-builds→ alert when build time > 10× the last-week median for this project.all→ alert on every state transition (noisy — only useful while debugging the skill).
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.
- 1mo ago First seen · 85 lines · 0 tokens per session scan A 77ba967c3239
[REPLACE: SKILL_NAME] is a skill published in the GitHub repository aeonfun/aeon (777 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,274 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.
Other skills, from other repositories
flowcraft-config
Author, validate, and troubleshoot complete FlowCraft configuration: deployment documents (deploy.yaml with the runtime section, inference/workspace/sandbox/tool sub-documents, core/memory contracts, and graph JSON node wiring), craft.yaml application definitions, and plugin.json manifests. Use when writing or…
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
agent-cloud-architect
Specialist subagent: Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes…
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
hello
What the hello plugin contributes to anvil; handed to agents by the host.