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 CodeInfinity1/Stram --skill wakeup-schedulinggit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/wakeup-scheduling)<a href="https://agentmods.dev/skills/codeinfinity1/stram/wakeup-scheduling"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/wakeup-scheduling/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/codeinfinity1/stram/wakeup-scheduling"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/wakeup-scheduling.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.00045 | $0.00638 |
| Opus 5.5 | $0.00018 | $0.00255 |
| Sonnet 5.5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
wakeup-scheduling 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wakeup Scheduling
Purpose
Manage future stimuli for the assistant in a bounded, auditable way. This skill adapts reminder and scheduling patterns from external reference Apple Reminders and external reference calendar/scheduling skills into Stram triggers and wakeups.
When To Use
Use when the user asks to remind, check later, follow up, monitor, continue tomorrow, run a future task, or cancel a scheduled wakeup.
Inputs And Evidence
- User-stated trigger condition or time.
- Existing trigger and wakeup status.
- Commitments and related task context.
- Channel or response-mode constraints.
Tool Map
cognitive_trigger_recordcognitive_trigger_statuscognitive_trigger_evaluatecognitive_trigger_cancelcognitive_commitment_statusautomation_daemon_status
Workflow
- Clarify whether the user wants a one-time reminder, recurring monitor, conditional trigger, or task continuation.
- Inspect existing triggers to avoid duplicates.
- Record a trigger with clear name, text, source, and reason.
- If a commitment is related, link the wakeup context in the reason or evidence.
- For cancellation, use exact trigger ID where possible.
- Verify the trigger appears in status and explain how it will fire.
Safety And Boundaries
- Do not schedule external-visible actions without explicit approval.
- Do not create vague recurring monitors with no stop condition.
- Do not infer exact dates from ambiguous words without the current date/time context.
Safety And Approval
- Confirm ambiguous dates, times, recurrence, timezone, and stop conditions before recording a wakeup.
- Do not schedule live sends, purchases, deletes, installs, deploys, or other external-visible actions without explicit approval.
- For monitors, record the trigger condition, cadence, maximum scope, and what should happen when it fires.
- Cancellation should use exact trigger IDs when available and should not delete unrelated reminders.
Native Implementation Boundaries
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 · 77 lines · 45 tokens per session scan A 7c7cc0f184a4
wakeup-scheduling is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 638 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
ask-agents
Send a task or question to Claude Code and/or Gemini as external subagents and report back what they said. Use when the user asks to ask Claude, ask Gemini, ask both, get a second opinion, split reviewer roles, or compare external agents.
review-plan
Review a proposed plan with a single-pass structured critique and a clear verdict. Use when the user asks to review a plan, stress-test a plan, critique a workflow, identify risks, or improve an execution sequence.
alive:settings
The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…
lark-contact
A Feishu (Lark) contacts tool for finding users or bots and looking up their profiles and contact details.
oci-services-expert
Expert guidance on Oracle Cloud Infrastructure services, architecture patterns, cost optimization, and deployment strategies. Use when designing on OCI, selecting OCI services, estimating cost, or applying OCI enterprise best practices.
openai-agentkit
Build production multi-agent systems with OpenAI AgentKit and the Agents SDK — orchestration, handoffs, and routines. Use when writing agents against OpenAI's AgentKit/Agents SDK or porting an agent design to the OpenAI stack.