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/conversationnpx skills add DailybotHQ/deepworkplan-skill --skill conversationgit clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skillWrote 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/conversation)<a href="https://agentmods.dev/skills/dailybothq/deepworkplan-skill/conversation"><img src="https://agentmods.dev/badge/skills/dailybothq/deepworkplan-skill/conversation.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.00111 | $0.02874 |
| Opus 5 | $0.00056 | $0.01437 |
| Sonnet 5 | $0.00022 | $0.00575 |
| Haiku 4.5 | $0.00011 | $0.00287 |
Grade A, and why
dailybot-conversation 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 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.
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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dailybot Conversations
Requires
dailybot-cli >= 3.7.0(the skill-pack baseline; thedailybot conversation opencommand itself shipped in 3.2.0). Ifdailybot --versionreports lower, ask the developer to rundailybot upgradeand continue with your primary task meanwhile. See../SKILL.md§ Required Dailybot CLI version.
You help developers open a private Slack group DM (MPIM) that includes the Dailybot bot plus one or more teammates, and — in the same step — optionally post a message or report to that group. Opening is idempotent: the same set of participants always returns the same channel, so "open it, or reuse the existing one" is a single call. This is the natural first half of "start a group with Jane and Bob and send them the report."
This is distinct from dailybot-chat (which sends to an already-known
channel, DM, or team) and from dailybot-channels (which lists report-channel
UUIDs for form/check-in authoring). If the developer already has a channel id and
just wants to post, route to chat. If they want to create/obtain a group of
people, start here.
When to Use
- "Open a group DM with Jane and Bob" / "start a Slack group with the release team and the bot"
- "Open a group with
<user>and send them this report / analysis / summary" - "Get me a channel with these three people so the bot can post there"
- Any flow that needs a group channel id before posting — this command returns it (creating the group if needed, reusing it if it already exists)
Do not use this for posting to an existing channel/DM (→ chat), for discovering report channels (→ channels), or on non-Slack orgs (the command returns a clear "Slack only" error).
Auth model & permissions
POST /v1/open-conversation/ accepts either an org API key (X-API-KEY) or a
login Bearer token (dailybot login) — the CLI prefers the API key and falls
back to the Bearer token, the same header logic as chat send. Two server-enforced
gates:
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 · 244 lines · 111 tokens per session scan A 083dbdffffd9
dailybot-conversation is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 111 tokens to every session and 2,874 once invoked, about $0.0006 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.