agentmods.dev

aidevops: Command for Claude Code

.agents/scripts/commands/check-routines.md

check-routines is a command for Claude Code from marcusquinn/aidevops. It costs 10 tokens per session (406 once invoked), scanned A, original, MIT.

A command that checks the health of aidevops routine schedulers, the system services that run recurring automated tasks.

In plain words
What is it for?
Use it to view scheduler status, get a machine-readable report, explain likely causes, or safely repair certain stale macOS and Linux scheduler entries.
Why use it?
It helps find stopped or outdated schedules, failed service state, and differences between deployed routines and their source files.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: agent in frontmatter; mentions subagents; installed under .agents/ (shared by several agents).

This is marcusquinn/aidevops's own configuration. It tells Claude Code how to work on aidevops itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aidevops configures →

Part of the aidevops plugin — 13 skills, 128 commands shipped together

not rated 392repo +1 today A scan 10 tokens original MIT
View source ↗ marcusquinn/aidevops aidevops.sh
Reuse

Borrowing it

Nothing to install: this file belongs to marcusquinn/aidevops. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/marcusquinn/aidevops/main/.agents/scripts/commands/check-routines.md
Clone the repo
git clone --depth 1 https://github.com/marcusquinn/aidevops

Made for: Claude Code.

Or install aidevops, the plugin that ships this one along with the rest of its 13 skills, 128 commands.

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.

agentmods badge for check-routines

README.md
[![agentmods](https://agentmods.dev/badge/commands/marcusquinn/aidevops/check-routines.svg)](https://agentmods.dev/commands/marcusquinn/aidevops/check-routines)
Your own site
<a href="https://agentmods.dev/commands/marcusquinn/aidevops/check-routines"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/check-routines.svg" alt="Measured on agentmods" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 406 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00406
Opus 5 $0.00005 $0.00203
Sonnet 5 $0.00002 $0.00081
Haiku 4.5 $0.00001 $0.00041

Measured 8d ago against content hash cd1eb933e14d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

check-routines 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 8d 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.

.agents/scripts/commands/check-routines.md · 55 lines

What it actually says

Check aidevops routine scheduler health across macOS launchd and Linux systemd.

Arguments: $ARGUMENTS

Use the routines-health subagent

Delegate interpretation to @routines-health when the report shows stale units, failed scheduler state, version drift, or migration symptoms.

Default command

~/.aidevops/agents/scripts/routines-health-helper.sh check $ARGUMENTS

Common invocations

# Read-only status
~/.aidevops/agents/scripts/routines-health-helper.sh check

# Machine-readable summary
~/.aidevops/agents/scripts/routines-health-helper.sh check --json

# Explain likely causes and repair commands
~/.aidevops/agents/scripts/routines-health-helper.sh explain

# Safe self-healing only: stale unmanaged dashboard launchd/systemd cleanup
~/.aidevops/agents/scripts/routines-health-helper.sh repair-safe

# Focus dashboard routine migration checks
~/.aidevops/agents/scripts/routines-health-helper.sh check --routine r912

Report expectations

  • Platform scheduler state: launchd pulse on macOS, user systemd pulse on Linux.
  • Routines source of truth: routines TODO enabled/disabled entries.
  • Deployment drift: deployed agents version versus source checkout version.
  • Known stale scheduler hazards: dashboard r912 disabled/unmanaged while legacy scheduler files still exist.

Repair policy

  • check and explain are read-only.
  • repair-safe may stop/disable and move/remove stale unmanaged dashboard scheduler files only when r912 is disabled or unmanaged.
  • Broader destructive repairs require explicit operator review and should be implemented through /full-loop.
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.

  1. 8d ago First seen · 55 lines · 10 tokens per session scan A cd1eb933e14d

Subscribe to this mod's changes

check-routines is a command published in the GitHub repository marcusquinn/aidevops (392 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 406 once invoked, about $0.0001 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.

DevOps and cloudagentsagents-mdaiai-agentsdevops-tools
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens