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/activity/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/activity)<a href="https://agentmods.dev/skills/egregore-labs/egregore/activity"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/activity/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/activity"><img src="https://agentmods.dev/badge/skills/egregore-labs/egregore/activity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 109 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00063 | $0.00661 |
| Opus 5.5 | $0.00025 | $0.00264 |
| Sonnet 5.5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
activity 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 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.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity
Use this bounded status card only when the user names Activity or directly asks
to display its dashboard/card. "Explicit" means display intent, not merely a
question about the team. Questions asking for explanation or synthesis of
current focus, themes, priorities, or work use attached
EGREGORE_ORG_CONTEXT_V1 evidence or exactly one Search workflow query when
that evidence is absent. The same applies to returning to earlier work. Never
use Activity as discovery or analysis fallback.
Render the team view immediately. The renderer's stdout IS the product card: fully visible the moment rendering finishes, appearing exactly once in the conversation. Never copy, regenerate, summarize, or repeat the card — or any of its rows — in your reply. The card's own closing question is the prompt for the next turn; after the command, add nothing beyond an answer to something the user separately asked.
When to invoke
Explicit Activity card only. Use when the user names /activity or directly asks to show, open, or render the Activity dashboard/card. Never use it to answer or synthesize what the team is focused on, busy with, prioritizing, or doing; analytical organizational questions use Search/Runtime QMD.
Read path
Fetch exactly one authorized Runtime snapshot and render it:
bash bin/activity-data.sh 2>/dev/null \
| bash bin/node-run.sh bin/codex-skill-render.mjs activity-card -
Do not sync repositories, query memory again, or call implementation infrastructure directly. The snapshot already contains bounded canonical sessions, questions, quests, todos, and lifecycle-resolved handoffs. Canonical Markdown/Git wins over every projection.
Connected enrichment is a separate capability-authorized adapter. Use it only
when the user explicitly asks for Connected/projected status by setting
EGREGORE_STATUS_CONNECTED_ENRICH=1 for the same single data command. Never
replace canonical lifecycle fields with the returned projection payload.
Handoff actions
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 · -194 lines · +20 tokens per session 435bb475f957
- 1mo ago First seen · 263 lines · 43 tokens per session scan A b5edf570f170
activity is a skill published in the GitHub repository egregore-labs/egregore (293 stars, last pushed 9d ago), licensed MIT. It adds 63 tokens to every session and 661 once invoked, about $0.0003 per session on Opus 5.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
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…
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
ulw-execute
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.