Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add duthaho/skillhub/plugin install dailyWrote 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/duthaho/skillhub/daybrief)<a href="https://agentmods.dev/skills/duthaho/skillhub/daybrief"><img src="https://agentmods.dev/badge/skills/duthaho/skillhub/daybrief.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.1 | $0.00170 | $0.02276 |
| Opus 5 | $0.00085 | $0.01138 |
| Sonnet 5 | $0.00034 | $0.00455 |
| Haiku 4.5 | $0.00017 | $0.00228 |
Grade A, and why
daybrief 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daybrief — morning work briefing
/daybrief [plain-language steering, e.g. "skip email", "just repos", "save it"]
Answer one question in one scan: what needs my attention today, in what order? Pull every source in parallel, compress hard, and lead with the priorities — not the raw data. Target: the user reads it in under two minutes.
Step 0 — Config
Look for daybrief-config.md in the current working directory. It defines:
# daybrief config
## Repos # absolute paths, or workspace roots to scan one level deep
- /home/hop/code
## Tasks # optional: where your todos live (any/all of these)
- file: TODO.md # a local markdown todo file (path relative to a repo or absolute)
- github: assigned # issues assigned to you, via `gh` if authenticated
## Radar topics # 2–4 topics to check for movement
- claude code
- postgres
## Preferences
- timezone: Asia/Ho_Chi_Minh
- email: on # on / off
- calendar: on # on / off
- save: off # on = also write brief to out/daybrief/ (enables carry-over)
If missing, don't block: run with what's inferable (current repo, no radar
topics). Then, after delivering the brief, offer to create the config via a
short interview — ask (in one compact question set, prefilled with what you
learned this run): which repos/workspace roots to watch, 2–4 radar topics, where
todos live (file path / GitHub / none), email & calendar on/off, and whether to
save briefs (save: on enables carry-over). Confirm the timezone from the
system rather than asking. Write daybrief-config.md from the answers and
remind that it's gitignored. If the user declines, don't ask again on later
runs — just note "no config" in the footer. Honor one-off steering from the
arguments over the config.
Step 1 — Gather all sources in parallel
Launch everything concurrently. Each source is independent and optional — if its tools aren't connected or it errors, mark it "unavailable" in the brief footer and move on. Never let one dead source stall the brief.
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.
- 7d ago First seen · 191 lines · 170 tokens per session scan A fce61ae03a3e
daybrief is a skill published in the GitHub repository duthaho/skillhub (9 stars, last pushed 13d ago), licensed MIT. It adds 170 tokens to every session and 2,276 once invoked, about $0.0009 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-31.
Other skills, from other repositories
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
phx-freeze
Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
042-planning-openspec
Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an…
043-planning-github-issues
Use when you need GitHub CLI (gh) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for…