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 bytesagain/ai-skills --skill autohotkeygit clone --depth 1 https://github.com/bytesagain/ai-skillsWrote 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/bytesagain/ai-skills/autohotkey)<a href="https://agentmods.dev/skills/bytesagain/ai-skills/autohotkey"><img src="https://agentmods.dev/badge/skills/bytesagain/ai-skills/autohotkey/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/bytesagain/ai-skills/autohotkey"><img src="https://agentmods.dev/badge/skills/bytesagain/ai-skills/autohotkey.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.00037 | $0.00273 |
| Opus 5 | $0.00018 | $0.00137 |
| Sonnet 5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
autohotkey 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 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.
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.
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.
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 · 36 lines · 37 tokens per session scan A e2ddfa148f93
autohotkey is a skill published in the GitHub repository bytesagain/ai-skills (13 stars, last pushed 4mo ago), with no licence file. It adds 37 tokens to every session and 273 once invoked, about $0.0002 per session on Opus 5. 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-09-03.
Other skills, from other repositories
automations
Schedule or manage recurring and one-shot BB agent or script automations.
workflow
A workflow skill for embedded-device projects that plans and runs building, flashing, debugging, observing, and diagnosis tasks.
hatch3r-cli-toolbox
Category-indexed reference for 34 specialist CLI tools beyond the always-on five (ripgrep, jq, gh, fd, fzf). Use to pick the right tool for HTTP clients, ai-chat, structural-search, sed-style edits, data ops, browser automation, container ops, and more.
meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.
calendar-followup
Surface unfinished follow-ups from last week's external meetings. Trigger when the user asks "who do I need to follow up with", "what meetings haven't I followed up on", or as part of the morning briefing ritual.
follow-up
Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".