What is mc-manage-automations?

A manager for recurring agent tasks stored in a scheduler configuration file. Recurring tasks are jobs that run automatically on a timetable, such as daily or weekly.

Use it to schedule, list, edit, or remove recurring tasks, while keeping single-collection data refreshes in that collection's own configuration.

It avoids manually starting repeated checks, digests, notifications, or cleanup jobs.

mc-manage-automations — Skill for Claude Code and Codex by receptron

Install

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.

Any agent

npx skills add receptron/mulmoclaude --skill mc-manage-automations

Clone the repo

git clone --depth 1 https://github.com/receptron/mulmoclaude

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-manage-automations/github.svg)](https://agentmods.dev/skills/receptron/mulmoclaude/mc-manage-automations)

Your own site

<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-manage-automations"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-manage-automations/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/receptron/mulmoclaude/mc-manage-automations"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/mc-manage-automations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 199 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,741 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00199	$0.01741
Opus 5	$0.00100	$0.00870
Sonnet 5	$0.00040	$0.00348
Haiku 4.5	$0.00020	$0.00174

Measured 12d ago against content hash 76ece25b713e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

mc-manage-automations 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.

packages/core/assets/skills-preset/mc-manage-automations/SKILL.md · 154 lines

How it starts

The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Automations manager

A bundled MulmoClaude preset skill (mc- prefix = launcher-managed; do not edit this file in the workspace, it is overwritten on every server boot).

Help the user schedule recurring agent tasks — the things that wake the agent up on a cron / interval to run a fixed prompt. State lives in a single JSON array at config/scheduler/tasks.json (cwd-relative; the agent runs with cwd set to the workspace root, so every path in this file is plain cwd-relative); the auto-refresh hook re-registers tasks after every Write/Edit so changes take effect immediately.

End with a one-line confirmation ("Scheduled weather-morning, daily 07:00 UTC." / "Stopped weekly-cleanup.") so the user can verify without scrolling.

First: is this just refreshing ONE collection?

Before writing a tasks.json automation, check what the recurring work actually is. If it's "keep one collection's records up to date" — refresh stock quotes, re-poll a set of watched URLs, pull fresh figures for every row — do NOT create an automation here. Add an ingest block to that collection's own schema.json instead:

"ingest": {
  "kind": "agent",
  "schedule": "daily",
  "atHour": 21,
  "role": "<a role that owns the tools the refresh needs>",
  "template": "templates/refresh.md"
}

and write templates/refresh.md telling the worker how to refresh the records. The full contract is in config/helps/collection-skills.md → "Scheduled agent refresh". On schedule (and on the collection's Refresh button) the host runs a hidden background worker that edits the records.

Prefer this over a tasks.json automation whenever the work is one collection's refresh: the schedule lives with the collection — it travels when the skill is copied and is deleted when the collection is, instead of leaving an orphan task here whose prompt points at records that may no longer exist. (Editing data/stock-quotes/items/*.json daily? That's ingest.kind: "agent" on the stock-quotes schema, not an automation.)

Read the full file on GitHub · 154 lines

Changes

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 · 154 lines · 199 tokens per session scan A 76ece25b713e

Subscribe to this mod's changes

mc-manage-automations is a skill published in the GitHub repository receptron/mulmoclaude (347 stars, last pushed today), licensed MIT. It adds 199 tokens to every session and 1,741 once invoked, about $0.0010 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.

Productivity

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…

nexu-io/open-design · 117 tokens

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…

danielmiessler/LifeOS · 196 tokens

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.

pinchtab/pinchtab · 52 tokens

mc-manage-automations