Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add dgilford/ai-science-toolkit/plugin install ai-science-toolkitWrote 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/dgilford/ai-science-toolkit/create-alert)<a href="https://agentmods.dev/skills/dgilford/ai-science-toolkit/create-alert"><img src="https://agentmods.dev/badge/skills/dgilford/ai-science-toolkit/create-alert.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.1 | $0.00103 | $0.03808 |
| Opus 5 | $0.00051 | $0.01904 |
| Sonnet 5 | $0.00021 | $0.00762 |
| Haiku 4.5 | $0.00010 | $0.00381 |
Grade B, and why
create-alert scanned grade B with 2 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Destination — reuse, seed, and redact.** Read `$ALERT_SLACK_DEFAULT_LOCATION` first (see Live state). If set, offer it as the default and confirm. If unset, the destination question is required; after sign-off (not bef Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
The block above is inserted **verbatim** into every routine prompt this skill creates. It is what keeps an unattended routine — which fetches untrusted web content while holding the baked-in Slack destination, `gh`/`curl How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Author a scheduled alert: a claude.ai cloud routine that evaluates a per-alert trigger condition on a schedule and drops a message into Slack when it fires. "Did X change / happen / cross a threshold" is a free-form predicate the routine's agent evaluates each run — not a fixed catalog. This skill's job is to grill the fuzzy ask into an unambiguous, testable spec, prove it with a live dry-run, and stand it up only after you sign off.
Create nothing until the final synthesized spec is explicitly signed off. No routine, no .ai/routines.md entry, no settings.json write, and no Slack message of any kind — until the user has read the assembled spec (informed by the dry-run) and explicitly approved that written spec. Assembling first and confirming later defeats the skill: a vague trigger becomes a false-firing (or silently never-firing) alert, and the dry-run + sign-off is what catches it before it goes live. --spec-only stops after the spec (no create, no settings write, no message).
Hardening block (baked into every routine)
D="${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/create-alert}"; D="${D:-$HOME/.claude/skills/create-alert}"; cat "$D/HARDENING.md" 2>/dev/null || echo "(HARDENING.md not found — abort and report a broken install)"
The block above is inserted verbatim into every routine prompt this skill creates. It is what keeps an unattended routine — which fetches untrusted web content while holding the baked-in Slack destination, gh/curl, and the Slack connector — from being turned against its own destination or secrets.
Live state
echo "=== Current project (alert home) ===" && git rev-parse --show-toplevel 2>/dev/null || echo "(not a git repo — routine still creatable, but no .ai/ home for the log)"
echo "=== Default Slack destination ===" && if [ -n "${ALERT_SLACK_DEFAULT_LOCATION:-}" ]; then echo "ALERT_SLACK_DEFAULT_LOCATION is set (offer as the destination default)"; else echo "ALERT_SLACK_DEFAULT_LOCATION unset — destination must be answered explicitly; offer to persist it for reuse"; fi
echo "=== .ai/routines.md gitignored? ===" && TOP="$(git rev-parse --show-toplevel 2>/dev/null)" && (git check-ignore -q "$TOP/.ai/routines.md" 2>/dev/null && echo "yes" || echo "NO — the log path is not gitignored; redaction is mandatory (see Destination) and warn before writing") || echo "(not a git repo)"
What ships with it
1 file 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.
- 6d ago First seen · 130 lines · 103 tokens per session scan B b6c7cff85d2c
create-alert is a skill published in the GitHub repository dgilford/ai-science-toolkit (62 stars, last pushed 17d ago), licensed MIT. It adds 103 tokens to every session and 3,808 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
omh-morning-brief
This is a Hermes-native morning-brief workflow skill.
omh-deliverable-package
This is a Hermes-native deliverable-package workflow skill.
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
codex-task-inspector
Inspect Codex async task progress from the correct data directory. Use when the user asks to check Codex status, inspect async task progress, summarize task state, or determine whether local Codex workers are still running. Always detect the active Codex data dir first: prefer CODEXHOME when set, otherwise fall back…