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 agentmods add skills/codeinfinity1/stram/wakeup-schedulingnpx skills add CodeInfinity1/Stram --skill wakeup-schedulinggit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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 | $0.00045 | $0.00638 |
| Opus 5 | $0.00023 | $0.00319 |
| Sonnet 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 2d 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.
- 2d ago First seen · 77 lines · 45 tokens per session scan A 7c7cc0f184a4
wakeup-scheduling is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 45 tokens to every session and 638 once invoked, about $0.0002 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.