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 maxnorm/magento2-agent-skills --skill magento-cronjob-developergit clone --depth 1 https://github.com/maxnorm/magento2-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/maxnorm/magento2-agent-skills/magento-cronjob-developer)<a href="https://agentmods.dev/skills/maxnorm/magento2-agent-skills/magento-cronjob-developer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-cronjob-developer/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/maxnorm/magento2-agent-skills/magento-cronjob-developer"><img src="https://agentmods.dev/badge/skills/maxnorm/magento2-agent-skills/magento-cronjob-developer.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.00054 | $0.01507 |
| Opus 5 | $0.00027 | $0.00754 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
magento-cronjob-developer 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Magento 2 Cron Job Developer
Expert specialist in creating reliable, efficient scheduled tasks and background processes that automate critical business operations while maintaining system performance and reliability.
When to Use
- Creating scheduled tasks
- Implementing background processing
- Automating system operations
- Building data synchronization jobs
- Implementing maintenance tasks
- Creating notification systems
Cron Job Architecture
- Cron Configuration: Master crontab.xml configuration and job scheduling
- Job Classes: Implement robust job execution classes and error handling
- Schedule Management: Design flexible scheduling patterns and intervals
- Resource Management: Optimize memory and processing resource usage
- Dependency Management: Handle job dependencies and execution order
Cron Development Process
1. Job Planning & Design
- Requirements Analysis: Understand business requirements and execution patterns
- Performance Planning: Plan for expected load and resource requirements
- Error Scenarios: Identify potential failure points and recovery strategies
- Monitoring Strategy: Plan logging, alerts, and performance tracking
- Integration Points: Design integration with existing systems and processes
2. Configuration Setup
- Crontab Configuration: Configure job scheduling in
etc/crontab.xml - Group Organization: Organize jobs into logical groups and categories
- Schedule Definition: Define appropriate execution intervals and timing
- Resource Allocation: Plan memory limits and execution timeouts
- Environment Configuration: Configure for different environments
3. Job Implementation
- Job Class Development: Create robust job execution classes
- Business Logic: Implement core job functionality and operations
- Data Processing: Handle data validation, transformation, and storage
- Error Handling: Implement comprehensive error handling and logging
- Progress Tracking: Create progress monitoring and status reporting
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.
- 10d ago First seen · 196 lines · 54 tokens per session scan A dd770b6ae56b
magento-cronjob-developer is a skill published in the GitHub repository maxnorm/magento2-agent-skills (29 stars, last pushed 7mo ago), licensed MIT. It adds 54 tokens to every session and 1,507 once invoked, about $0.0003 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.
Other skills, from other repositories
magento2-backend-dev
This skill should be used when the user asks to "create an API endpoint", "build a REST API", "add a GraphQL resolver", "create a CLI command", "add a cron job", "set up a message queue", "implement a web API", "add a SOAP service", or "create a data provider". Covers Magento 2 backend development: REST/SOAP/GraphQL…
magento-agent-amqp
Autonomously diagnose Magento 2 message queue problems — backlog growth, stuck consumers, broker connectivity, DLQ overflow — and scaffold new queues (communication, topology, consumer, publisher) from a specification. Produces an AMQP Report with root cause and fix.
magento-agent-api-builder
Autonomously generate a complete Magento 2 REST or GraphQL API from a plain-language spec — service contracts, repository, webapi.xml, and GraphQL schema with resolvers.
magento-agent-module-generator
Autonomously generate a complete, production-ready Magento 2 module from a plain-language spec — all files, directory structure, service contracts, and database schema.
magento-amqp
Configure Magento 2 message queues with AMQP (RabbitMQ, AmazonMQ), DB adapter, and all four required XML files. Use when building async processing, bulk operations, or decoupled architectures.
magento-api
Create Magento 2 REST and GraphQL API endpoints following service contract patterns. Use when building APIs, webapi.xml routes, or GraphQL resolvers.