Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillnpx agentmods add skills/dailybothq/deepworkplan-skill/chatWrote 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/dailybothq/deepworkplan-skill/chat)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/chat"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/chat/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/chat"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/chat.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.09491 |
| Opus 5.5 | $0.00042 | $0.03796 |
| Sonnet 5.5 | $0.00021 | $0.01898 |
| Haiku 4.5 | $0.00010 | $0.00949 |
Grade A, and why
dailybot-chat 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 — 739 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dailybot Chat
Requires
dailybot-cli >= 3.9.0(the skill-pack baseline). Thedailybot chat send/chat updatecommand group — including--thread-message, login-Bearer auth on/v1/send-message/,--send-as-user/--send-as-me, and the full interactive-button surface (--buttons, approval / workflow-button flags, modals, callbacks) — is available at this floor. Ifdailybot --versionis below 3.9.0, ask the developer to rundailybot upgrade. See../SKILL.md§ Required Dailybot CLI version for install commands and version-check tooling.
You send Dailybot bot messages on the developer's behalf to the organization's connected chat platform (Slack, Microsoft Teams, Discord, Google Chat) — to user DMs, channels, or whole teams (expanded to member DMs server-side). This skill is the right surface for:
- A short heads-up to a channel ("deploy started")
- A report-style post: a short headline in the channel + the full detail in its thread, in a single call (keeps the channel clean, groups the context, looks like a real human update)
- Pinging one or several teammates by DM
- Editing a previously sent message in place — including any individual thread reply
It is not:
dailybot-report— that posts progress updates to the Dailybot dashboard (no Slack/Teams delivery by default).dailybot-email— that sends transactional email.dailybot-messages— that polls inbound agent-to-agent messages.
If the developer wants to "tell the team in Dailybot" generically, prefer dailybot-report. Route to dailybot-chat only when they explicitly mention chat / Slack / Teams / Discord / Google Chat, or a channel id / channel name, or want a message visible inside the chat tool itself.
When to Use
Trigger phrases the agent should recognize:
Send (channels / users / teams):
- "send a Slack message to #releases", "post to channel C0123"
- "DM Carolina that the build is green", "ping Sergio Florez in chat"
- "broadcast this to the Engineering team in Slack"
- "post a deploy summary to #releases with the changelog as a thread"
- "send a chat message to the QA team"
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 Changed fba9a0280757
- 4d ago Changed 03a0f5d2704e
- 5d ago Changed ea5fab39f254
- 10d ago Changed 9505cc81a51e
- 15d ago Changed f3057d9a023d
- 18d ago Changed c9ee007870f9
- 21d ago Changed 2670dedca074
- 1mo ago Changed · +205 lines · +14 tokens per session 2c95f7cebec7
- 1mo ago First seen · 534 lines · 90 tokens per session scan A b9828d9a90df
dailybot-chat is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (23 stars, last pushed 3d ago), licensed MIT. It adds 104 tokens to every session and 9,491 once invoked, about $0.0004 per session on Opus 5.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
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
dependency-upgrade
Plan, batch, and verify dependency upgrades safely. Triages outdated packages into risk tiers, upgrades in order (dev/minor/patch first, runtime majors last), verifies each batch, and produces an auditable commit sequence. Use when asked to "upgrade deps", "bump packages", "update nodemodules", "fix vulnerabilities"…
forensics
Post-mortem a failed GSD auto-mode run. Traces symptom to root cause via .gsd/ activity, journal, metrics, and lock artifacts, producing a filing-ready bug report with file:line refs and a fix suggestion. Use when asked to "forensics", "post-mortem", "why did auto-mode fail", "trace the stuck loop", "debug the crash"…
review
Review code changes for security, performance, bugs, and quality. Reviews staged changes, unstaged changes, specific commits, or PR-ready diffs.