Borrowing it
Nothing to install: this file belongs to Everyone-Needs-A-Copilot/claude-copilot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Everyone-Needs-A-Copilot/claude-copilot/main/.claude/skills/sales/daily-briefing/SKILL.mdgit clone --depth 1 https://github.com/Everyone-Needs-A-Copilot/claude-copilotWrote 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/everyone-needs-a-copilot/claude-copilot/daily-briefing)<a href="https://agentmods.dev/skills/everyone-needs-a-copilot/claude-copilot/daily-briefing"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/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/everyone-needs-a-copilot/claude-copilot/daily-briefing"><img src="https://agentmods.dev/badge/skills/everyone-needs-a-copilot/claude-copilot/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.00068 | $0.01675 |
| Opus 5.5 | $0.00027 | $0.00670 |
| Sonnet 5.5 | $0.00014 | $0.00335 |
| Haiku 4.5 | $0.00007 | $0.00168 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Sales Briefing
Get a clear view of what matters most today. This skill works with whatever you tell me, and gets richer when you connect your tools.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ DAILY BRIEFING │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: today's meetings, key deals, priorities │
│ ✓ I organize: prioritized action plan for your day │
│ ✓ Output: scannable 2-minute briefing │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + Calendar: auto-pull today's meetings with attendees │
│ + CRM: pipeline alerts, tasks, deal health │
│ + Email: unread from key accounts, waiting on replies │
│ + Enrichment: overnight signals on your accounts │
└─────────────────────────────────────────────────────────────────┘
Getting Started
When you run this skill, I'll ask for what I need:
If no calendar connected:
"What meetings do you have today? (Just paste your calendar or list them)"
If no CRM connected:
"What deals are you focused on this week? Any that need attention?"
If you have connectors: I'll pull everything automatically and just show you the briefing.
Connectors (Optional)
Connect your tools to supercharge this skill:
| Connector | What It Adds |
|---|---|
| Calendar | Today's meetings with attendees, times, and context |
| CRM | Open pipeline, deals closing soon, overdue tasks, stale deals |
| Unread from opportunity contacts, emails waiting on replies | |
| Enrichment | Overnight signals: funding, hiring, news on your accounts |
No connectors? No problem. Tell me your meetings and deals, and I'll create your briefing.
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.
- 1mo ago First seen · 264 lines · 68 tokens per session scan A 9f2c4976aed1
daily-briefing is a skill published in the GitHub repository Everyone-Needs-A-Copilot/claude-copilot (14 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 1,675 once invoked, about $0.0003 per session on Opus 5.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
RemoteTeamCommander
Complete operating system for remote and distributed teams — async communication, time zone equity, virtual culture, performance management at a distance, and preventing remote-class citizens.
request-progress
Group recent conversations into overall requests, review each one's progress from memory, link each to the owner goals it serves, and write the build story, so My Work shows progress meters, shipping velocity and learned working preferences. Use when asked to "group requests", "group by overall request", "review…
slack
Read and search messages, channels, and threads in the user's Slack workspace. Use to catch up on team discussions and decisions, post channel messages, and reply to coworkers through Slack's official MCP server.
onboard
Onboarding doc for a new contributor or agent — project state, conventions, priorities relevant to the specified role.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…