background-check

background-check is a skill for Claude Code, Codex from smixs/iva-agent. It costs 32 tokens per session (594 once invoked), scanned A, original, MIT.

A status-checking skill for long-running background jobs, such as scheduled scripts or external processing tasks. It reads a limited status or log snapshot and reports whether the job is complete, running, failed, or unknown.

In plain words
What is it for?
It is for checking scheduled jobs, investigating interrupted memory tasks, reading recent service logs, and reporting what remains or caused a failure.
Why use it?
It avoids leaving a conversation open while waiting and avoids treating a process ID as proof that work finished. It preserves failure details and checkpoints when a job stops.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It is for checking scheduled jobs, investigating interrupted memory tasks, reading recent service logs, and reporting what remains or caused a failure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/smixs/iva-agent/background-check
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 smixs/iva-agent --skill background-check
Clone the repo
git clone --depth 1 https://github.com/smixs/iva-agent

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.

agentmods badge for background-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/smixs/iva-agent/background-check/github.svg)](https://agentmods.dev/skills/smixs/iva-agent/background-check)
Your own site
<a href="https://agentmods.dev/skills/smixs/iva-agent/background-check"><img src="https://agentmods.dev/badge/skills/smixs/iva-agent/background-check/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.

agentmods 80×15 button for background-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/smixs/iva-agent/background-check"><img src="https://agentmods.dev/badge/skills/smixs/iva-agent/background-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 594 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.00032 $0.00594
Opus 5.5 $0.00013 $0.00238
Sonnet 5.5 $0.00006 $0.00119
Haiku 4.5 $0.00003 $0.00059

Measured yesterday against content hash 5a837eed5897, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

agent/skills/background-check/SKILL.md · 41 lines

What it actually says

Check a background job

A check observes a job; it does not keep a model turn open until the job finishes.

  1. Read a bounded status snapshot: the job's checkpoint/progress file, a short tail of its log, or systemctl --user show <unit> -p ActiveState -p SubState -p Result -p ExecMainStatus. For the cause, read journalctl --user -u <unit> -n 50 --no-pager. A PID alone does not prove progress or completion. Use a short tool timeout; no sleep, tail -f, status checks in a loop or wait for process exit.
  2. Return the observed state and its evidence: completed, still running, failed or unknown. Still running means say what remains; never report it as complete. Stop checking after that snapshot. A Reminder returns the status as its final text: code delivers it. Do not send the report yourself, invent a keepalive or create another Reminder inside that turn. Arrange a later check only in the owner's chat, if asked.
  3. A failed custom script: preserve its output and resume checkpoint, find the failing input and show the cause before suggesting a restart. Colliding PDF basenames need a job-owned temporary directory and unique paths per input, not overwriting /tmp/<basename>. A restart can repeat external side effects; establish resume safety and the owner's authorization first.
  4. An interrupted memory-night: read iva diagnose and its Schedules section, the failed job's log, the raw day in vault/daily/ and its cache in data/memory/night/. A day not processed that night is not proof that a Card was deleted. The next night resumes an unfinished day from its cache. Never delete that cache, raw days or Cards to repair a provider timeout; never switch the night model behind the owner's back. Restore the configured provider, then check the next run. iva jobs ack acknowledges a failure; it does not perform the missing work. If bytes are actually missing, preserve the files and Git evidence and load report-problem.

Existing Watch and Brief read failures of user timer services and installed plugin/MCP services. They do not supervise arbitrary detached processes, detect a hung but live process, or restart a custom script. Keep a persistent capability in a plugin, and use a Routine for recurring work; do not build another scheduler or watchdog in the chat. Before fixing a Watch failure, follow watch: read-only until the owner's Fix tap.

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 Changed 5a837eed5897
  2. 7d ago First seen · 41 lines · 32 tokens per session scan A 0318f5308a2c

Subscribe to this mod's changes

background-check is a skill published in the GitHub repository smixs/iva-agent (240 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 594 once invoked, about $0.0001 per session on Opus 5.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-10-09.