dailybot-custom-form-template

A starter template for creating a custom Dailybot form skill in a repository.

In plain words
What is it for?
Use it as a reference when copying and adapting a custom skill for a specific Dailybot form.
Why use it?
It provides the expected file location and configuration pattern so custom form behaviour is kept separate from files replaced during Dailybot upgrades.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/dailybothq/deepworkplan-skill/_custom-template
Any agent
npx skills add DailybotHQ/deepworkplan-skill --skill _custom-template
Clone the repo
git clone --depth 1 https://github.com/DailybotHQ/deepworkplan-skill

Made for: Claude Code, Codex.

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,352 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00076 $0.01352
Opus 5 $0.00038 $0.00676
Sonnet 5 $0.00015 $0.00270
Haiku 4.5 $0.00008 $0.00135

Measured 3d ago against content hash c63469ba12ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dailybot-custom-form-template scanned grade A with 0 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 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/dailybot/forms/_custom-template/SKILL.md · 130 lines

How it starts

The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Custom Form Skill — Starter Template

[!IMPORTANT] Do not use this file in place. It lives inside the universal Dailybot skill pack (.agents/skills/dailybot/) only as a reference. Copy it to your own repo as:

.agents/skills/dailybot-custom/<your-skill-name>/SKILL.md

The universal Dailybot skill pack is managed by skills-lock.json and rewritten on every upgrade. Anything you place inside .agents/skills/dailybot/ will be overwritten. Anything under .agents/skills/dailybot-custom/ is customer-owned and the installer never touches it. That separation is the entire point — keep the line clean.


When the universal skill loads this custom file

The universal dailybot-forms skill resolves a per-form custom skill by reading .dailybot/profile.json in the repo root and looking up the current form under vars.custom_form_skills:

{
  "vars": {
    "custom_form_skills": {
      "by_uuid": {
        "<form-uuid-in-this-environment>": ".agents/skills/dailybot-custom/<your-skill-name>"
      },
      "by_slug": {
        "<form-slug-stable-across-environments>": ".agents/skills/dailybot-custom/<your-skill-name>"
      }
    }
  }
}

When either lookup matches, the universal skill stops and loads this file. Everything below this point is your custom workflow logic — write it for the specific form this skill targets.


1 — Auth

User-scoped Bearer token (dailybot login). This is identical to the universal forms skill — see ../../shared/auth.md. If the developer doesn't have a session, fall back to the universal skill's auth steps; don't reinvent them here.


2 — State machine reference (fill in)

Document the workflow this form uses. Read it from dailybot form get <form_uuid> --json once and pin the canonical version here so future-you doesn't have to re-derive it.

draft  → review     "Send for review"
review → released   "Mark released"
review → draft      "Back to draft"
released → (final, sticky unless allow_reopen_from_final_state=true)

Read the full file on GitHub · 130 lines

Changes

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.

  1. 3d ago First seen · 130 lines · 76 tokens per session scan A c63469ba12ef

Subscribe to this mod's changes

dailybot-custom-form-template is a skill published in the GitHub repository DailybotHQ/deepworkplan-skill (20 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,352 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens