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 fergupa/claude_plugins --skill daily-briefinggit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/daily-briefing)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/daily-briefing"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/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/fergupa/claude_plugins/daily-briefing"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/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 fergupa/claude_plugins (2 stars, last pushed 8mo ago), licensed Apache-2.0. 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
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…