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 pincerhq/pincer --skill scheduler-briefingsgit clone --depth 1 https://github.com/pincerhq/pincerWrote 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/pincerhq/pincer/scheduler-briefings)<a href="https://agentmods.dev/skills/pincerhq/pincer/scheduler-briefings"><img src="https://agentmods.dev/badge/skills/pincerhq/pincer/scheduler-briefings/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/pincerhq/pincer/scheduler-briefings"><img src="https://agentmods.dev/badge/skills/pincerhq/pincer/scheduler-briefings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00056 | $0.00448 |
| Opus 5 | $0.00028 | $0.00224 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
Scheduler and proactive briefings 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.
What it actually says
Scheduler and proactive briefings
Pincer has two proactive systems, both driven by a persistent SQLite-backed scheduler:
Morning briefings
A daily briefing is generated per user with up to four sections: weather
(OpenWeatherMap), calendar (reuses the calendar tool), email (reuses the
email tool), and news (NewsAPI), plus any custom sections the user has
configured. Settings live in a briefing_config table per
pincer_user_id:
sections— which of weather/calendar/email/news are includedcustom_sections— user-defined additionsweather_location— e.g."Berlin,DE"news_topics— e.g.["technology", "business"]
The briefing time and timezone are global config (briefing_time,
default 07:00, and briefing_timezone), not per-user.
If the user wants to change what's in their briefing, update their
briefing_config row rather than the global schedule.
Cron scheduler
General-purpose scheduling uses standard cron expressions, persisted so
schedules survive restarts, checked every 60 seconds, timezone-aware per
schedule. Action handlers are registered by type (briefing, custom,
etc.) — when a user asks "remind me every Monday at 9am to...", this is
the mechanism to use: create a schedule with a cron expression and an
action, not an ad-hoc sleep/loop.
Event triggers (reactive, not scheduled)
Separate from cron, event triggers fire on external events rather than on a schedule: new email arrival, calendar reminders (15 minutes before an event), and custom webhooks. Deduplication prevents the same event from notifying twice. Use these when the user wants "notify me when X happens" rather than "do X at time Y".
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 · 46 lines · 56 tokens per session scan A eb2db2078cd1
Scheduler and proactive briefings is a skill published in the GitHub repository pincerhq/pincer (50 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 448 once invoked, about $0.0003 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.