Borrowing it
Nothing to install: this file belongs to Koroqe/OPOS. 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/Koroqe/OPOS/main/.claude/skills/list-scheduled-processes/SKILL.mdgit clone --depth 1 https://github.com/Koroqe/OPOSWrote 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/koroqe/opos/list-scheduled-processes)<a href="https://agentmods.dev/skills/koroqe/opos/list-scheduled-processes"><img src="https://agentmods.dev/badge/skills/koroqe/opos/list-scheduled-processes/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/koroqe/opos/list-scheduled-processes"><img src="https://agentmods.dev/badge/skills/koroqe/opos/list-scheduled-processes.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.00058 | $0.01628 |
| Opus 5 | $0.00029 | $0.00814 |
| Sonnet 5 | $0.00012 | $0.00326 |
| Haiku 4.5 | $0.00006 | $0.00163 |
Grade A, and why
list-scheduled-processes 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 9d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
list-scheduled-processes
When to use
To inventory the current scheduling state of the company OR to detect drift between PROCESS.md declarations and Claude Code's live cron registrations. Invoke as /list-scheduled-processes (no arguments).
Read-only. Does NOT modify cron registrations, the local cache, or any PROCESS.md. Safe to run on a fresh machine — CronList is the authoritative source of live registrations for runtime: claude-schedule, NOT the local .claude/scheduled-processes.json cache. For runtime: cloud (v0.14) the authoritative source is RemoteTrigger {action: "list"}: a declared-cloud process is LIVE when a routine named opos-<process-name> exists AND is enabled (disabled → report DISABLED, not MISSING — it was unscheduled, not lost); cross-check its cron_expression against the declaration (remembering the UTC shift + jitter) for DRIFT; surface next_run_at and, for failure triage, point at {action: "list_runs", trigger_id} → {action: "get_run_log", session_id}. For runtime: gha (v0.10) the authoritative source is the workflow file: a declared-gha process is LIVE when .github/workflows/opos-<process-name>.yml exists (cross-check its cron against the declaration for DRIFT); best-effort, also surface the last run's conclusion via gh run list --workflow opos-<name>.yml --limit 1 and warn when the ANTHROPIC_API_KEY secret is absent (gh secret list).
Prerequisite: the user must be logged into Claude Code (claude login). CronList authenticates against the user's subscription.
Inputs
None.
Steps
- Glob and parse PROCESS.md candidates. Glob
**/PROCESS.mdrooted at repo root. For each, parse frontmatter and categorize:- Declared (valid): all 4 scheduling fields present AND
ui.scheduling.validate_frontmatterreturns(True, []). Recordprocess_name,schedule,authority,path. - Declared (invalid): at least 1 scheduling field present but
validate_frontmatterreturned errors. Recordprocess_name,path, and the error list. - Undeclared: none of the 4 scheduling fields present. Skip (manual-only process — not relevant to this inventory).
- Declared (valid): all 4 scheduling fields present AND
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 72 lines · 58 tokens per session scan A 11591de16e30
list-scheduled-processes is a skill published in the GitHub repository Koroqe/OPOS (2 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 1,628 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-31.
Other skills, from other repositories
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
backend-scheduling-cron
Use this skill when the user says 'cron', 'schedule', 'scheduled task', 'cron job', 'job scheduling', 'distributed cron', 'cron expression', 'timezone', 'scheduler', 'background job', 'periodic task', 'interval', 'cron trigger'. This skill implements distributed cron and job scheduling with timezone-aware triggers and…
workflow-extract
Baut aus einem Chatverlauf oder aus bestehenden Automatisierungs-Prompts (z. B. eines anderen Agenten-Systems) eine selbstlaufende, user-neutrale Workflow-Automatisierung: einen wiederkehrenden Prompt bzw. Automations-Skill für Cron/Schedule/Loop. Alias: automations-extractor. Nutze diesen Skill bei „mach daraus eine…
c-cron
Manage cron jobs and macOS launchctl services — schedule recurring tasks, start/stop services using lunchy-go.
convex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
Scheduling work
Put work on the user's schedule, and read, amend or stop what is already there, using the scheduler tools.