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.
npx skills add dayfinggg/openai-codex-agent-skills --skill background-job-changegit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/background-job-change)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/background-job-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/background-job-change/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/dayfinggg/openai-codex-agent-skills/background-job-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/background-job-change.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.00031 | $0.00360 |
| Opus 5.5 | $0.00012 | $0.00144 |
| Sonnet 5.5 | $0.00006 | $0.00072 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
background-job-change 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 today.
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.
What it actually says
Verify the worker's delivery contract and side effects.
- Establish the queue or scheduler, client and broker versions, message shape, acknowledgment policy, concurrency, and worker lifecycle. Read both producers and consumers of the changed event.
- Determine the actual delivery semantics and what happens after a process crash. Do not assume exactly-once execution from an acknowledgment setting or deduplication name.
- Trace writes, external effects, and acknowledgment relative to commit. Define idempotency at the business operation where required. Repeating a non-idempotent external request needs a supported reconciliation strategy.
- Distinguish transient and permanent failures. Preserve supported event types, ordering requirements, and retry policy. Bound attempts, time, and concurrency using existing operational constraints.
- Check poison-message handling, dead-letter or failed-job retention, cancellation, and graceful shutdown. Do not acknowledge work before its durable result unless the established contract intentionally does so.
- Make the smallest correction. Reuse the existing queue framework and transactional outbox or deduplication mechanism when present. Do not introduce a new broker for a local reliability issue.
- Verify the normal path, duplicate delivery, relevant partial failure, exhausted retry, and interruption between the side effect and acknowledgment. Inspect observable state and message lifecycle rather than only handler return values.
Read the broker and framework documentation matching installed versions. For PHP testing, read the PHP testing procedure. Use symfony-diagnostics for Symfony-specific operational evidence when needed. Finish with the original delivery contract preserved or an explicitly requested contract change verified.
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.
- today First seen · 18 lines · 31 tokens per session scan A 264fcdcf3eb9
background-job-change is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 360 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-30.
Other skills, from other repositories
ubiquitous-language
Maintain a project thesaurus (domain glossary) following DDD ubiquitous language principles. Use PROACTIVELY when naming anything: variables, functions, classes, modules, database fields, API endpoints, events, files, or directories. Also use when the user asks to "create thesaurus", "update glossary", "add term"…
neo4j-getting-started-skill
Orchestrates zero-to-running-app in 8 stages — prerequisites → context → provision → model → load → explore → query → build. Each stage reads its own reference file. Supports HITL and fully autonomous operation. Use when starting a new Neo4j project from scratch, provisioning Aura, generating synthetic data, building…
neo4j-graphql-skill
Build and configure a GraphQL API backed by Neo4j using @neo4j/graphql v7 (current) or v5 (LTS). Covers Neo4jGraphQL constructor, getSchema(), assertIndexesAndConstraints(), type definitions with @node, @relationship (IN/OUT/UNDIRECTED), @cypher for custom resolvers, @authorization/@authentication for JWT/JWKS…
neo4j-kafka-skill
Configure and operate the Neo4j Connector for Kafka (sink + source) and the native Neo4j CDC API. Covers Cypher/Pattern/CUD sink strategies, CDC-based and query-based source, exactly-once semantics, DLQ error handling, Confluent Cloud managed connector, schema registry (Avro/JSON), and native db.cdc.query cursor-loop…
kirby-plugin-development
Builds or extends Kirby plugins using hooks, extensions, blocks, KirbyTags, and shared templates/controllers. Use when creating reusable features or integrating Panel customizations.
kirby-scaffold-page-type
Scaffolds a Kirby 6 page type (blueprint + template, optional controller/model) using project roots, index tools, and value/display field references. Use when creating or extending a page type.