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/channelsnpx skills add DailybotHQ/deepworkplan-skill --skill channelsgit 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.00058 | $0.00822 |
| Opus 5 | $0.00029 | $0.00411 |
| Sonnet 5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
dailybot-channels 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dailybot Report Channels
Requires
dailybot-cli >= 3.7.0(the skill-pack baseline). Thedailybot channels listcommand is available at this floor. Ifdailybot --versionreports below 3.7.0, ask the developer to rundailybot upgrade. See../SKILL.md§ Required Dailybot CLI version.
Report channels are the Slack / Microsoft Teams / Discord / Google Chat
destinations where Dailybot posts form and check-in reports. This sub-skill lists
the channels available to you so their UUIDs can be attached to a form or check-in
with --report-channel during authoring.
Auth model — API key or login
Works under a login session (Bearer) or an org API key (DAILYBOT_API_KEY).
Visibility is role-scoped server-side; the CLI never client-filters.
When to Use
- The developer is authoring a form or check-in (see
../forms/SKILL.md§ Authoring and../checkin/SKILL.md§ Authoring) and needs a channel UUID for--report-channel. - The developer asks "which channels can Dailybot post to?".
Do not use this to send a message to a channel — that's dailybot-chat.
Step 1 — List channels
# Human-readable table
dailybot channels list
# Machine-readable (recommended for agents)
dailybot channels list --json
JSON shape:
[
{"uuid": "abc123-def456", "name": "#engineering", "platform": "slack", "channel_id": "C0123ABCDEF"}
]
Step 2 — Use a channel UUID in authoring
dailybot form create -n "Sprint Retro" --report-channel abc123-def456
dailybot checkin config <followup_uuid> --report-channel abc123-def456
--report-channel is repeatable to attach multiple channels.
Non-Blocking Rule
If the CLI is unavailable or unauthenticated, surface the issue once and continue;
never block work on channel discovery. The HTTP fallback is
GET /v1/report-channels/ (see ../shared/http-fallback.md).
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.
- 3d ago First seen · 76 lines · 58 tokens per session scan A 238e9660c095
dailybot-channels is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 822 once invoked, about $0.0003 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.
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…