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-briefnpx skills add uselessspace/freedeepagents-activity-builder --skill activity-briefgit 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-brief)<a href="https://agentmods.dev/skills/uselessspace/freedeepagents-activity-builder/activity-brief"><img src="https://agentmods.dev/badge/skills/uselessspace/freedeepagents-activity-builder/activity-brief.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.1 | $0.00120 | $0.00790 |
| Opus 5 | $0.00060 | $0.00395 |
| Sonnet 5 | $0.00024 | $0.00158 |
| Haiku 4.5 | $0.00012 | $0.00079 |
Grade A, and why
activity-brief 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 6d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity Brief
何时用：刚有活动点子、需求还模糊时。只问清需求、不碰文件 → 产出 Brief 后交
/activity-classifier。
Own the first stage of building a FreeDeepAgents activity. Do not scaffold or edit files until the brief is clear enough to classify.
What To Clarify
Capture the smallest useful brief:
activity_type_id: kebab-case candidate, orunknownif not chosen yet.display_name: human-facing activity name.target_user: who uses it and in what setting.core_loop: what the user provides, what the agent returns, and what repeats.success_experience: what a good first successful run feels like.interaction_model: card buttons, forms, uploads, chat, long-running view, or a combination.frontend_need: no dedicated frontend, static preview, visual canvas, dashboard, game-like interaction, timeline, graph, or other.agent_navigation: whether a successful Agent read/action should switch the user's open Static Preview to an activity-private route, view, or business object; otherwisenone. This is not browser click/scroll automation.image_need: none, generate fresh images, or edit user/reference images.document_need: none, accept files only, or let the Agent parse supported documents withread_document.audio_need: none, SPA direct ASR, Agent-turn ASR, TTS, voice clone, or a combination.spa_interaction: none, deterministic handlers, Preview Agent Turns, or both. Use Agent Turns only when the action needs model understanding, Skills, planning, or multiple tools.external_capabilities: APIs, databases, browser/search, files, payments, models, or other services.persistence: growing/queryable records (SQLite by default), small Prompt-aware typed-KV state, hybrid storage, larger artifacts, secrets, or none.
Conversation Style
Ask compact questions. Prefer one grouped message with 5-7 concrete prompts over a long questionnaire. If the user already gave enough information, infer reasonable defaults and state them.
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.
- 6d ago First seen · 86 lines · 120 tokens per session scan A 0876aee4032d
activity-brief is a skill published in the GitHub repository uselessspace/freedeepagents-activity-builder (2 stars, last pushed 18d ago), licensed MIT. It adds 120 tokens to every session and 790 once invoked, about $0.0006 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…