Awesome Claude Code Toolkit is a curated collection of extensions and configuration for Claude Code, including agents, skills, commands, plugins, hooks, rules, templates, MCP configurations, and companion apps. It is for Claude Code users who want ready-made workflows and integrations for different development tasks. The catalogue add-ons are selected components from this toolkit.
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.
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkitWrote 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/commands/rohitg00/awesome-claude-code-toolkit/create-cron)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/create-cron"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/create-cron.svg" alt="Measured on agentmods" 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.00000 | $0.00295 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
create-cron 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 5d 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.
What it actually says
/create-cron - Create Cron Job
Configure a cron job with proper scheduling and error handling.
Steps
- Ask the user for the task description and desired schedule
- Translate the schedule description to cron syntax (minute hour day month weekday)
- Show the next 5 execution times to verify the schedule is correct
- Create the cron job script with proper error handling and logging
- Add a lock mechanism to prevent overlapping executions
- Configure output redirection: stdout to log file, stderr to error log
- Add environment variable setup at the top of the cron script
- Set up email or webhook notification for job failures
- Add a health check: alert if the job has not run within expected interval
- Install the cron job using crontab or systemd timer
- Verify the job is listed in the cron table
- Document the job: purpose, schedule, log location, notification settings
Rules
- Always use absolute paths in cron scripts (PATH is minimal in cron)
- Set a timeout to kill hung jobs (use timeout command)
- Use file locking (flock) to prevent overlapping executions
- Redirect output to log files; do not rely on cron mail
- Include the full environment setup in the script (PATH, HOME, etc.)
- Add a comment line above each cron entry describing its purpose
- Test the cron script manually before installing it
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.
- 5d ago First seen · 29 lines · 0 tokens per session scan A 1487c53bc7c3
create-cron is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,598 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 295 tokens. 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.
Other commands, from other repositories
create-prompt
Create a new prompt that another Claude can execute.
design
A command for choosing or defining the visual style of a PowerPoint presentation, including its colors, fonts, and page layouts. It offers preset styles, custom brand settings, and recommendations based on the presentation topic.
checklist
Generate a custom checklist for the current feature based on user requirements.
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.
specify
Create or update the feature specification from a natural language feature description.
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.