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/uselessspace/freedeepagents-activity-builder/activity-buildernpx skills add uselessspace/freedeepagents-activity-builder --skill activity-buildergit clone --depth 1 https://github.com/uselessspace/freedeepagents-activity-builderWrote 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/uselessspace/freedeepagents-activity-builder/activity-builder)<a href="https://agentmods.dev/skills/uselessspace/freedeepagents-activity-builder/activity-builder"><img src="https://agentmods.dev/badge/skills/uselessspace/freedeepagents-activity-builder/activity-builder.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.00051 | $0.01389 |
| Opus 5 | $0.00026 | $0.00694 |
| Sonnet 5 | $0.00010 | $0.00278 |
| Haiku 4.5 | $0.00005 | $0.00139 |
Grade A, and why
activity-builder 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity Builder
何时用:Brief + Classification 都齐、要真正写文件时。Static Preview 前端完成后或 Card-only 实现完成后,都先交
/activity-review。
Own scaffold and implementation. Require both Activity Brief and
Activity Classification before changing files.
Shared References
Use the package assets relative to this skill:
../../workflows/02-author-backend.mdfor backend scaffold and host skill.../../workflows/03-image-tooling.mdwhenimage_axisis notnone.../../workflows/04-derive-frontend.mdwhenfrontend_axisisstatic-preview.../../references/user-upload.mdfor end-user uploads;../../references/preview-agent-turns.mdfor structured SPA actions needing model understanding, Skills, planning, or multiple tools.../../references/preview-asr.mdwhen the SPA needs a transcript immediately without creating an Agent turn; use upload +attachment_refswhen the Agent must own the recording instead.../../policies/capabilities.mdplus the capability-specific reference for every value in Classificationruntime_capabilities.../../references/asset-lifecycle.mdfor replace/delete/durability semantics.../../references/preview-navigation.mdforagent-to-preview.../../references/handler-context-lifecycle.mdbefore work may outlive a tool/handler call.../../workflows/06-verify-directory.mdfor verification expectations.../../workflows/07-migrate-existing.mdwhen the user wants to fork an existing activity.../../references/card-block-types.md— read before writing cards; it owns the 6 block schemas, form semantics, and form-vs-action decision.../../references/card-system-tools.mdfor the canonicalcard_emit_template/artifact_emit/memory_addtool signatures and a worked example.../../policies/output-protocol.mdfor the card-system transport contract.../../policies/manifest-allowed-fields.mdfor manifest field whitelist.../../policies/runtime-boundary.mdand../../policies/skill-layering.mdfor hard boundaries.../../references/store-mode-table.mdfor persistent image URLs.../../references/data-mode-selection.mdfor SQLite/typed-KV/hybrid/none.../../references/sqlite-storage.mdwhenever Classification enables SQLite.
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 · 121 lines · 51 tokens per session scan A 1266f3961592
activity-builder is a skill published in the GitHub repository uselessspace/freedeepagents-activity-builder (2 stars, last pushed 16d ago), licensed MIT. It adds 51 tokens to every session and 1,389 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-31.
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…