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/reportnpx skills add DailybotHQ/deepworkplan-skill --skill reportgit 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.00047 | $0.05533 |
| Opus 5 | $0.00023 | $0.02766 |
| Sonnet 5 | $0.00009 | $0.01107 |
| Haiku 4.5 | $0.00005 | $0.00553 |
Grade B, and why
dailybot-report scanned grade B with 2 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| Claude Code | `grep -q "dailybot-auto-activation" ~/.claude/CLAUDE.md 2>/dev/null && echo "installed"` | 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 — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dailybot Progress Report
You help developers keep their team informed. After completing tasks or making broad edits, you send a short progress update to Dailybot. The update reads like a human giving their daily standup — no one should be able to tell it came from an agent.
Agent Compatibility
This skill works across all major AI coding agents. Execution paths differ slightly but the logic is identical.
| Agent | Skill path | Activation |
|---|---|---|
| Claude Code | ~/.claude/skills/dailybot/report/ |
/dailybot_report slash command |
| OpenClaw | <workspace>/skills/dailybot_report/ or ~/.openclaw/skills/ |
/dailybot_report slash command |
| Cursor | ~/.cursor/skills/dailybot/report/ |
Natural language trigger |
| OpenAI Codex | ~/.codex/skills/dailybot/report/ |
Natural language trigger |
| Windsurf | ~/.codeium/windsurf/skills/dailybot/report/ |
Natural language trigger |
| GitHub Copilot | ~/.copilot/skills/dailybot/report/ |
Natural language trigger |
| Cline | ~/.cline/skills/dailybot/report/ |
Natural language trigger |
| Gemini CLI | ~/.gemini/skills/dailybot/report/ |
Natural language trigger |
When natural language triggers apply, the skill activates on phrases like: "report this to Dailybot", "send a Dailybot update", "let my team know what we built".
Step 0 — Optional Auto-Activation Setup (First Run Only)
Auto-activation makes Dailybot reporting fire automatically in future sessions
without the developer invoking the skill each time. It is opt-in. Writing
to a global agent config file (CLAUDE.md, AGENTS.md, etc.) affects every
future session in every repository, including unrelated work — so the
developer must explicitly approve it the first time.
There are two independent opt-ins, and you should consider both every first run:
- Step 0a — Prompt trigger (works on every agent): a standing instruction in the global config file.
- Step 0b — Hook enforcement (harnesses with a hook system): deterministic, harness-driven reminders.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 536 lines · 47 tokens per session scan B a143d182b9e6
dailybot-report is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 5,533 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.
agent-upkeep
Perform one small, scoped maintenance improvement to the Elements monorepo and open a single reviewable pull request. Use this skill for scheduled or unattended upkeep runs that improve unit test coverage for one file, fix one behavioral bug in one module, or move one off ESLint rule toward enforcement to reduce…
organize-project
Organise documents into folders and move them between folders and modules with MOVE. Use when a module has grown unstructured, when restructuring a project, or when a document is in the wrong place.