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/validate-schedule)<a href="https://agentmods.dev/commands/rohitg00/awesome-claude-code-toolkit/validate-schedule"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/validate-schedule/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/commands/rohitg00/awesome-claude-code-toolkit/validate-schedule"><img src="https://agentmods.dev/badge/commands/rohitg00/awesome-claude-code-toolkit/validate-schedule.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.00000 | $0.00340 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
validate-schedule 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
/validate-schedule - Validate Cron Schedule
Validate and explain a cron schedule expression.
Steps
- Take the cron expression from the user (5 or 6 fields)
- Parse each field: minute, hour, day of month, month, day of week
- Validate syntax: check for valid ranges, step values, and special characters
- Detect common mistakes: day/month confusion, 0-indexed vs 1-indexed weekdays
- Translate the expression to plain English description
- Calculate the next 10 execution times based on the current date
- Calculate the frequency: how many times per day, week, month
- Identify potential issues: running too frequently, not running at expected times
- Check for timezone considerations and DST transition impacts
- Suggest alternative expressions if the schedule could be simplified
- Compare with common cron presets: @hourly, @daily, @weekly, @monthly
- Display a visual calendar showing execution times for the next 30 days
Rules
- Support both 5-field (standard) and 6-field (with seconds) cron formats
- Validate ranges: minutes (0-59), hours (0-23), days (1-31), months (1-12), weekdays (0-7)
- Handle both numeric and named values for months and weekdays
- Warn about expressions that run more than 100 times per day
- Note timezone implications for jobs that span midnight or DST boundaries
- Detect mutually exclusive day-of-month and day-of-week combinations
- Support extended cron syntax: L (last), W (weekday), # (nth weekday)
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 db421a2fd024
validate-schedule 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 340 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.