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 daxaur/openpaw --skill c-briefinggit clone --depth 1 https://github.com/daxaur/openpawWrote 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/daxaur/openpaw/c-briefing)<a href="https://agentmods.dev/skills/daxaur/openpaw/c-briefing"><img src="https://agentmods.dev/badge/skills/daxaur/openpaw/c-briefing.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.00030 | $0.00623 |
| Opus 5 | $0.00015 | $0.00311 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade B, and why
c-briefing scanned grade B 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 8d 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.
cat > ~/.claude/briefing.sh << 'SCRIPT' How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Briefing
Compile a morning summary from your installed skills. Checks what's available and builds the briefing accordingly.
What to Include
Check which skills are installed and pull from each:
| If installed | Include in briefing |
|---|---|
| c-email | Unread email count + top 5 subjects |
| c-calendar | Today's events + tomorrow preview |
| c-tasks | Due today + overdue items |
| c-notes | Recently modified notes |
| c-github | Open PRs, review requests, CI failures |
| c-slack | Unread DM count + mentions |
| c-tracking | Package delivery updates |
Briefing Format
Good morning, {name}! Here's your briefing for {date}:
📧 Email: 12 unread — 3 flagged
→ "Q4 Budget Review" from Sarah
→ "Deploy approval needed" from CI Bot
→ "Lunch tomorrow?" from Mike
📅 Calendar:
→ 9:00 AM Team standup (30 min)
→ 11:00 AM 1:1 with Alex (45 min)
→ 2:00 PM Sprint review (1 hr)
✅ Tasks: 3 due today, 1 overdue
→ [overdue] Fix login bug
→ Write API docs
→ Review PR #234
🔔 Other:
→ 2 GitHub PRs need review
→ Package arriving today (Amazon)
Scheduled Briefing
To run automatically each morning, set up a launchd job (macOS) or cron job:
# Create a briefing script
cat > ~/.claude/briefing.sh << 'SCRIPT'
#!/bin/bash
claude --print "Run my daily briefing using the c-briefing skill. Be concise." \
| terminal-notifier -title "Morning Briefing" -message "Ready" 2>/dev/null
SCRIPT
chmod +x ~/.claude/briefing.sh
# Schedule with cron (every weekday at 8:00 AM)
(crontab -l 2>/dev/null; echo "0 8 * * 1-5 ~/.claude/briefing.sh") | crontab -
# Or use lunchy-go for launchd (macOS)
lunchy-go install ~/.claude/briefing.plist
Manual Briefing
Just ask Claude: "Give me my daily briefing" or "What's on my plate today?"
Guidelines
- Read the user's name from SOUL.md or MEMORY.md
- Only include sections for skills that are actually installed
- Keep it concise — no section should exceed 5 items
- Flag urgent items at the top
- Include the date and day of week
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.
- 8d ago First seen · 81 lines · 30 tokens per session scan B 5a3c672e85d9
c-briefing is a skill published in the GitHub repository daxaur/openpaw (167 stars, last pushed 3mo ago), licensed MIT. It adds 30 tokens to every session and 623 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
ibrahim-daily-briefing
Generate Ibrahim's daily briefing — new leads, upcoming calls, pending follow-ups, system health, and one strategic question. Delivered to Telegram.
work-log-codex
A workflow for turning Codex and Claude Code session records into readable Markdown work logs. It can organize activity by project and date range, such as today, this week, or a custom period.
shell-scripting
A guide to writing Bash shell scripts, which automate command-line tasks on Linux and similar systems. It covers variables, arrays, conditions, loops, functions, and safer script structure.
cron
A guide to Cron, a Unix system that runs commands automatically at scheduled times. It explains crontab files, which store those schedules, along with time formats, service management, logs, and troubleshooting.
ansible
A guide for using Ansible, a tool that automates commands and configuration across multiple computers. It covers hosts, reusable playbooks, modules, permissions, and check mode.
apple-reminders
Create and manage Apple Reminders on macOS using AppleScript - set due dates, priorities, and lists.