Borrowing it
Nothing to install: this file belongs to egregore-labs/egregore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/egregore-labs/egregore/main/.claude/skills/announce/SKILL.mdgit clone --depth 1 https://github.com/egregore-labs/egregoreWrote 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/egregore-labs/egregore/announce)<a href="https://agentmods.dev/skills/egregore-labs/egregore/announce"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/announce/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/egregore-labs/egregore/announce"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/announce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.01243 |
| Opus 5 | $0.00022 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
announce 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 10d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Send an announcement to the Telegram group. Drafts a message, shows a preview for approval, then sends.
When to invoke
User says: "announce", "tell the team", "send to the group", "notify everyone", "let everyone know"
Not this: notify one person → prepare a direct notification proposal · handoff → /handoff
Topic: $ARGUMENTS
What to do
Step 1: Draft the message
If $ARGUMENTS is provided, use it as the topic and draft a concise announcement (2-5 lines). Pull context from the conversation — what just happened, what changed, what the team should do.
If no arguments, ask: "What should I announce?"
Message guidelines:
- Lead with what changed (feature, fix, decision, merge)
- Include the PR number or branch if relevant
- End with an action if needed ("Run /update to get it", "Review PR #N", etc.)
- Keep it under 500 chars (chat readability)
- No emojis unless the user's draft uses them
Step 2: Publish artifact (if relevant)
If the announcement references a document, handoff, quest, or knowledge artifact from memory/, publish it now so the final message includes a clickable link with OG preview.
Detect: Check if the conversation produced or references a specific file in memory/ (handoffs, knowledge, quests). If so, publish it:
ARTIFACT_URL=$(bash bin/publish-artifact.sh document "$FILE_PATH" \
--title "$TITLE" \
--author "$AUTHOR" \
--description "$ONE_LINE_DESCRIPTION" 2>/dev/null)
Use the appropriate type: handoff, quest, or document (for knowledge files).
- If publish succeeds: insert the returned live URL into the message draft.
- If publish fails: send the message without a link. Do NOT make up a URL.
Never fabricate artifact URLs. Only use URLs returned by publish-artifact.sh.
Step 3: Plan, preview, and confirm
Follow .claude/context/notification-consent.md. Create the group plan only
after the artifact URL and message are final:
PLAN_JSON=$(bash bin/notify.sh plan group "$MESSAGE")
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.
- 10d ago First seen · 160 lines · 44 tokens per session scan A ae8dd9531c3b
announce is a skill published in the GitHub repository egregore-labs/egregore (289 stars, last pushed 6d ago), licensed MIT. It adds 44 tokens to every session and 1,243 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-08-30.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
xiaohongshu-image-creator
An image-making assistant for Xiaohongshu, a Chinese social platform for lifestyle, product, and educational posts. It creates vertical covers and supporting images matched to the post’s topic, audience, and visual style.
atomic-tdd
Test-first discipline. Auto-triggers on "let's implement X", "add feature Y", "fix bug Z", "write a test for", "implement", "build out", and similar pre-code-change phrases. Iron rule: failing test exists before production code. Skip only for pure docs/config changes with an explicit "skipped because:" note. Explicit…