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/dailybothq/deepworkplan-skill/workflownpx skills add DailybotHQ/deepworkplan-skill --skill workflowgit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillWhat 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.00073 | $0.01755 |
| Opus 5 | $0.00036 | $0.00877 |
| Sonnet 5 | $0.00015 | $0.00351 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
dailybot-workflow scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
metadata: {"openclaw":{"emoji":"🔀","homepage":"https://dailybot.com","requires":{"anyBins":["dailybot","curl"]},"primaryEnv":"DAILYBOT_API_KEY","install":[{"id":"cli-install-script","kind":"download","url":"https://cli. How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dailybot Workflows (read-only)
Requires
dailybot-cli >= 3.7.0(the skill-pack baseline). Thedailybot workflow list/dailybot workflow getcommand group is available. Ifdailybot --versionreports below 3.7.0, ask the developer to rundailybot upgrade. See../SKILL.md§ Required Dailybot CLI version for install commands and version-check tooling.
You help developers read the workflows configured for their organization. Workflows are Dailybot's automation objects (multi-step sequences that connect check-ins, forms, and chat actions). This skill is read-only — it lists workflows and reads one workflow's configuration so an agent can reference or explain them.
Writes are web-app only. Creating, editing, enabling, or deleting a workflow is done in the Dailybot web app — there is no CLI write path. Do not attempt to mutate a workflow from the CLI; if the developer wants to change one, point them at the Dailybot web app.
Plan-gated feature. Workflows are available on higher-tier plans. On a plan without them (and on the FREE plan generally) these reads return
403 plan_upgrade_requiredwith anupgrade_url— surface the upgrade path and stop. See../shared/list-query-and-errors.md§ 6.
Auth model — API key or login
Workflow reads accept either a Bearer login session (dailybot login)
or an org API key (DAILYBOT_API_KEY). Results are scoped to the acting
identity's permissions (the server resolves the API key's owner). See
../shared/list-query-and-errors.md § 6
for the full API-key ↔ Bearer parity and plan-gating rules.
When to Use
- "list my workflows", "show the org's workflows", "what workflows do we have?"
- "show me the release workflow", "what's configured in workflow X?"
- Another skill needs a workflow's UUID or its configuration for context.
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.
- 2d ago First seen · 187 lines · 73 tokens per session scan A 641d1499d812
dailybot-workflow is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,755 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.