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/cloudposse/atmos/saynpx skills add cloudposse/atmos --skill saygit clone --depth 1 https://github.com/cloudposse/atmosWhat 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.00058 | $0.00689 |
| Opus 5 | $0.00029 | $0.00345 |
| Sonnet 5 | $0.00012 | $0.00138 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
say 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 3d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audible Task Notifications
A written summary is easy to miss when it lands in a background session hours after the user stopped watching. This skill gives that moment an audible signal too.
When to use it
Two triggers, general-purpose — not tied to any one feature:
- A task or cycle finished in a way that needs human review (e.g. a fix was applied but the result deserves a second look).
- Execution is blocked and needs human input to proceed (e.g. a merge conflict, an ambiguous finding, a failure the caller correctly declined to touch).
Any skill or agent reaching one of these states should invoke this — it is not specific to
fix-all or any other single caller.
Phrasing rule
Keep it under ~15 words. Be specific, not a summary dump — include identifying context (a PR number, branch, or file) so the listener knows what without reading anything.
- Good:
"PR 2718 has a merge conflict, needs your attention." - Bad: a multi-sentence recap of the whole cycle.
Invocation
say is macOS-only. Wrap it defensively so a caller on another platform (or a machine without
say) never fails because of this notification. Build the message in a shell variable first, then
pass it via quoted expansion — never substitute untrusted text (a PR title, branch name, file
path) directly into the command source, since a stray " could terminate the quote and inject
additional shell content:
message="PR ${pr_number} needs your attention."
command -v say >/dev/null 2>&1 && say "$message" || true
No DATA-vs-instructions treatment is needed here: say only produces local audio output, no
state mutation, so it's exempt from the untrusted-content framing applied to things like
CodeRabbit comment bodies elsewhere in this repo's automation.
Requires .claude/settings.json → "Bash(say:*)" in allow — this skill owns that dependency;
callers don't need their own entry for it.
Related
fix-allskill — example caller, invokes this on every human-attention exit path in its check/fix cycle (scheduled hourly bypr-maintenance-loop, or run directly for a one-shot).test-coverageskill — example caller, invokes this when a test-fix attempt caps out still red or a coverage gap is genuinely untestable.lintskill — example caller, invokes this when a finding needs a broader refactor than patch scope allows.
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.
- 3d ago First seen · 63 lines · 58 tokens per session scan A 7db13de6a2ce
say is a skill published in the GitHub repository cloudposse/atmos (1,367 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 689 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
agency-os
Notion-as-source-of-truth dispatch board for running your work like an AI agency. One Tasks database is the source of truth; tasks flow Suggestion through Discussion, To-Do, In Progress, and Done with subtasks, recurring cadences, dependencies, and template subtrees. Batch execution fans approved To-Do rows out to…
maestro-bundle
Route work into the right maestro tier and drive the SPEC/NOTES/VERIFY bundle lifecycle - open, resume, close, recall.
tracecat-platform-guide
REQUIRED whenever the user asks what Tracecat is, what it can do, how to do something in the product, or where to find a feature in the UI — e.g. "how do I add a secret", "where are my integrations", "what's the difference between a case and a workflow", "can Tracecat send Slack messages", "how do I schedule a…
clawmax-mail
Use explicitly authorized Gmail or Microsoft 365 accounts for bounded inbox listing, search, reading, and unsent draft creation.