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 skills add desy-design/AG3NT --skill daily-briefinggit clone --depth 1 https://github.com/desy-design/AG3NTWrote 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/desy-design/ag3nt/daily-briefing)<a href="https://agentmods.dev/skills/desy-design/ag3nt/daily-briefing"><img src="https://agentmods.dev/badge/skills/desy-design/ag3nt/daily-briefing/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/desy-design/ag3nt/daily-briefing"><img src="https://agentmods.dev/badge/skills/desy-design/ag3nt/daily-briefing.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.00013 | $0.00445 |
| Opus 5 | $0.00006 | $0.00222 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
daily-briefing 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 12d 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.
This is a copy
100% identical to daily-briefing — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Daily Briefing
Generate a concise daily briefing for the user. This skill is typically triggered by a scheduled cron job at the start of the day.
Briefing Structure
- Good morning greeting (keep it brief)
- Today's date and day of week
- Reminders due today (if any scheduled)
- Tasks in progress (from your todo list)
- Key items to be aware of (based on recent context)
Response Format
☀️ Good morning!
📅 Today is [Day], [Date]
📋 Today's Focus:
- [Key tasks or reminders]
- [Any pending items]
🎯 Tip: [Optional - a brief productivity tip or encouragement]
Guidelines
- Be concise: Keep the briefing under 10 lines
- Only actionable items: Don't pad with fluff
- Positive tone: Start the day on a good note
- Skip sections: If there's nothing for a section, omit it entirely
- Context-aware: Reference recent conversations if relevant
Example Output
☀️ Good morning!
📅 Today is Monday, January 27th
📋 Today's Focus:
- Reminder: Team standup at 10am
- In progress: Code review for auth feature
- Pending: Reply to Alice's email
🎯 Have a productive day!
Integration Notes
This skill is designed to be triggered by a cron job configured like:
scheduler:
cron:
- schedule: "0 9 * * *" # 9 AM daily
message: "DAILY_BRIEFING"
sessionMode: "main"
name: "Morning Briefing"
The response will be sent to the user's primary channel.
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.
- 12d ago First seen · 80 lines · 13 tokens per session scan A 3667a13ee50a
daily-briefing is a skill published in the GitHub repository desy-design/AG3NT (2 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 445 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to daily-briefing, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
daily-briefing
Generate a daily briefing summary for the user.
heartbeat
Periodic system check for proactive updates and reminders.
system-info
Get system information including CPU usage, memory, disk space, battery status, and network info. Read-only and safe to use.
fleetq-manage-workflow
Build, validate, cost, and execute FleetQ visual DAG workflows — including generating one from a natural-language goal.
fleetq-run-experiment
Create, run, monitor, and recover a FleetQ experiment through its 20-state pipeline via MCP tools or the REST API.
fleetq-connect
Connect an agent to FleetQ over MCP or the REST API, including obtaining credentials via dynamic client registration.