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.00038 | $0.00613 |
| Opus 5.5 | $0.00015 | $0.00245 |
| Sonnet 5.5 | $0.00008 | $0.00123 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade B, and why
announce scanned grade B 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 24d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 tmp/announce-message.md How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Egregore announce
Draft one concise group message. The request authorizes drafting, never
dispatch or artifact publication. Reuse sufficient EGREGORE_ORG_CONTEXT_V1;
do not repeat organizational retrieval merely to decorate the message.
Preserve quoted wording exactly. Otherwise use 2–5 lines: what changed, the
relevant branch/artifact when already authorized, and the requested action.
Notification consent and publication consent are separate. Never publish a
referenced artifact automatically; publication is a separate
SHARE workflow with its own source/destination approval.
Write the final draft to tmp/announce-message.md, then
make the file private and prepare one actor-bound Runtime plan:
chmod 600 tmp/announce-message.md
bash bin/notification.sh plan --kind group --message-file tmp/announce-message.md > tmp/announce-plan.json
Read the plan's identifier and digest:
jq -r '.plan_id, .digest' tmp/announce-plan.json
Use the printed values as {plan_id} and {digest}, respectively; quote
placeholders in single quotes when you use them in a command, and write any
single quote inside a value as '\''.
Read the exact preview fields from the saved plan:
jq -r '.org, .recipient, .channels, .deliveries, .message' tmp/announce-plan.json
Show one dedicated Send / Edit / Cancel checkpoint containing the exact organization, group, every delivery/channel, and final message returned by the plan. Edit cancels the old plan before creating a new one. Cancel calls:
bash bin/notification.sh cancel '{plan_id}'
Only a fresh Send response for that exact checkpoint authorizes:
bash bin/notification.sh approve \
'{plan_id}' '{digest}' APPROVE_EXACT_NOTIFICATION --out tmp/announce-approval.json
Use {plan_id} from the saved plan; the adapter reads the private approval
receipt from tmp/announce-approval.json without exposing its credential:
bash bin/notification.sh dispatch '{plan_id}' --approval-file tmp/announce-approval.json
Report the returned delivery receipt. Never retry from old approval, change a destination, or fall back to another channel. Local instances without a notification capability stop after preview and return the text for manual use. The Runtime service owns ActorContext authorization, exact-plan binding, transport, and content-free telemetry.
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.
- 24d ago Changed · -84 lines · -6 tokens per session scan A → B 38d6edeb8171
- 1mo ago First seen · 160 lines · 44 tokens per session scan A ae8dd9531c3b
announce is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 38 tokens to every session and 613 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
handoff-protocols
Manages work transitions between team members or agents by creating structured handoff documents, summarizing project status, documenting key decisions, blockers, and open questions, and generating onboarding briefs. Use when someone needs to hand off, hand over, or transition a project; pass work to another person or…
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
bothread
Join and behave correctly in a Bothread room — a shared, human-governed space where you collaborate with other AI agents on one codebase. Use this when the user says they want you to join a Bothread session, gives you a Bothread session ID, or asks you to coordinate with other agents.
git-workflow
Git branching, commit conventions, rebase vs merge, conflict resolution, and release tagging. Use when setting up a git workflow, writing commits, resolving conflicts, or preparing a release.
mflow
Use when working in a repo that uses mflow, coordinating multiple AI agents/worktrees, setting up mflow sync, installing mflow MCP in Codex/Claude Code/Cursor/opencode, or before git operations where synced file changes may affect commits. Applies to CLI, MCP, room secrets, pause/resume, locks, status checks, and safe…