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/mubit-ai/claude-plugins/activitynpx skills add mubit-ai/claude-plugins --skill activitygit clone --depth 1 https://github.com/mubit-ai/claude-pluginsWrote 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/mubit-ai/claude-plugins/activity)<a href="https://agentmods.dev/skills/mubit-ai/claude-plugins/activity"><img src="https://agentmods.dev/badge/skills/mubit-ai/claude-plugins/activity.svg" alt="Measured on agentmods" 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 | $0.00045 | $0.01376 |
| Opus 5 | $0.00023 | $0.00688 |
| Sonnet 5 | $0.00009 | $0.00275 |
| Haiku 4.5 | $0.00005 | $0.00138 |
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 4d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill never installs anything, and it writes nothing anywhere unless asked. It runs one Node process from the plugin directory, makes one or more read-only calls to the configured instance, and prints the answer.
disable-model-invocation: true is deliberate, and matches dashboard. This is a question a
person asks about their own data; nothing in a conversation should decide on its own to pull a
copy of somebody's memory into the transcript. A disabled skill's description is not
always-loaded context either, so it costs nothing until somebody types it.
The distinction that decides which command to run
There are two things this command can produce and they are not the same kind of answer.
- A listing is a claim this client makes. The plugin sends the filters, and then checks the result against them itself: it re-drops derived entries and re-truncates content, and it says so when it had to. A listing is for reading.
- An export is the record the instance holds, byte for byte.
/v2/control/activity/exportaccepts noexclude_derivedand noprojectionat all, so an export is never filtered and never truncated, and nothing here reshapes it. An export is for keeping.
Never describe an export as "filtered activity". If somebody asks for "an export of my non-derived lessons", they are asking for two different operations: an export is everything in scope, and the filtering they want is a listing. Say which one they got.
Reading it
node "${CLAUDE_PLUGIN_ROOT}/bin/activity.mjs"
node "${CLAUDE_PLUGIN_ROOT}/bin/activity.mjs" --exclude-derived --type lesson
node "${CLAUDE_PLUGIN_ROOT}/bin/activity.mjs" --scan --since 2026-08-01T00:00:00Z
The default is one page of the newest activity for the newest run in this data directory.
--scan pages through everything that matches, oldest first. --run <id> picks a run and
--all-runs asks across every run the key can see.
Filters: --type (repeatable), --since / --until as RFC3339, --agent, --user, and
--exclude-derived for the entries the instance promoted for itself rather than ones a client
wrote. --full returns every field untruncated; the default is five keys per entry.
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.
- 4d ago First seen · 105 lines · 45 tokens per session scan A 7c32e975159f
activity is a skill published in the GitHub repository mubit-ai/claude-plugins (13 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 1,376 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…