pulse-check

pulse-check is a command for Codex from marcusquinn/aidevops. It costs 14 tokens per session (436 once invoked), scanned A, original, MIT.

A diagnostic command that checks worker activity and utilisation across repositories using current configuration and status data. It can also inspect a stalled issue and produce machine-readable output.

In plain words
What is it for?
Use it to check worker capacity, investigate stalled work, review recent activity, and file deduplicated self-improvement issues when requested.
Why use it?
It helps reveal whether available workers are being used and whether a specific task has stopped progressing.

Command for Codex

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

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.

agentmods
npx agentmods add commands/marcusquinn/aidevops/pulse-check
Clone the repo
git clone --depth 1 https://github.com/marcusquinn/aidevops

Made for: Codex.

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 pulse-check

README.md
[![agentmods](https://agentmods.dev/badge/commands/marcusquinn/aidevops/pulse-check.svg)](https://agentmods.dev/commands/marcusquinn/aidevops/pulse-check)
Your own site
<a href="https://agentmods.dev/commands/marcusquinn/aidevops/pulse-check"><img src="https://agentmods.dev/badge/commands/marcusquinn/aidevops/pulse-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00014 $0.00436
Opus 5 $0.00007 $0.00218
Sonnet 5 $0.00003 $0.00087
Haiku 4.5 $0.00001 $0.00044

Measured yesterday against content hash e8ff91ef9af8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pulse-check 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 yesterday.

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/pulse-check.md · 62 lines

What it actually says

Run a bounded pulse/worker productivity check for interactive sessions.

Arguments: $ARGUMENTS

Goal

Answer “is the pulse using available concurrency and model/provider allowance?” from canonical current-state evidence, not process snapshots or log mtimes.

Procedure

  1. Run the deterministic helper first:

    ~/.aidevops/agents/scripts/pulse-check-helper.sh report $ARGUMENTS
    
  2. If the user asks for machine-readable evidence:

    ~/.aidevops/agents/scripts/pulse-check-helper.sh json $ARGUMENTS
    
  3. If the report identifies a specific issue whose worker stopped progressing, inspect its bounded blocker lifecycle before opening raw logs:

    ~/.aidevops/agents/scripts/pulse-diagnose-helper.sh issue <N> --repo <owner/repo>
    
  4. If the user explicitly asks to file self-improvement work, or this is the scheduled daily routine, use deduplicated apply mode:

    ~/.aidevops/agents/scripts/pulse-check-helper.sh apply $ARGUMENTS
    

Interpretation

  • Prioritise 5–15 minute current-state evidence for “is work happening now?” claims.
  • Use 24h/48h aggregates only for trend context and failure-family clustering.
  • An issue is worth filing only when the helper marks a finding autofile=true or you can cite equivalent evidence from the helper JSON.
  • Do not publish private repo names, local paths, issue titles, or raw worker examples in public comments/issues; the helper output is aggregate by design.

Verification references

  • .agents/reference/diagnostics-discipline.md
  • .agents/reference/worker-diagnostics.md
  • .agents/scripts/tests/test-pulse-check-helper.sh
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. yesterday First seen · 62 lines · 14 tokens per session scan A e8ff91ef9af8

Subscribe to this mod's changes

pulse-check is a command published in the GitHub repository marcusquinn/aidevops (391 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 436 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-09-03.