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 furkangonel/cowrangler --skill schedulegit clone --depth 1 https://github.com/furkangonel/cowranglerWrote 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/furkangonel/cowrangler/schedule)<a href="https://agentmods.dev/skills/furkangonel/cowrangler/schedule"><img src="https://agentmods.dev/badge/skills/furkangonel/cowrangler/schedule.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.00088 | $0.00611 |
| Opus 5 | $0.00044 | $0.00305 |
| Sonnet 5 | $0.00018 | $0.00122 |
| Haiku 4.5 | $0.00009 | $0.00061 |
Grade A, and why
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 7d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
First, decide whether the user wants to create a new scheduled task or change an existing one.
Updating an existing task
If the user wants to reschedule, edit the prompt, or pause/resume a task that already exists, call the update_scheduled_task tool with its taskId — do not call create_scheduled_task. Use list_scheduled_tasks if you need to look up the ID. When this session is itself a scheduled run, the current task's ID is the name attribute in the <scheduled-task name="…"> tag at the top of the conversation.
Creating a new task
You are distilling the current session into a reusable shortcut. Follow these steps:
1. Analyze the session
Review the session history to identify the core task the user performed or requested. Distill it into a single, repeatable objective.
2. Draft a prompt
The prompt will be used for future autonomous runs — it must be entirely self-contained. Future runs will NOT have access to this session, so never reference "the current conversation," "the above," or any ephemeral context.
Include in the description:
- A clear objective statement (what to accomplish)
- Specific steps to execute
- Any relevant file paths, URLs, repositories, or tool names
- Expected output or success criteria
- Any constraints or preferences the user expressed
Write the description in second-person imperative ("Check the inbox…", "Run the test suite…"). Keep it concise but complete enough that another Claude session could execute it cold.
3. Choose a taskName
Pick a short, descriptive name in kebab-case (e.g. "daily-inbox-summary", "weekly-dep-audit", "format-pr-description").
4. Determine scheduling
The create_scheduled_task tool description explains the options (cronExpression for recurring, fireAt for one-time, omit both for ad-hoc) and their formats. If the user didn't give a clear schedule, propose one and ask them to confirm before proceeding.
Finally, call the create_scheduled_task tool.
Why/Failure Modes
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.
- 7d ago First seen · 60 lines · 88 tokens per session scan A 2c42b1c02714
schedule is a skill published in the GitHub repository furkangonel/cowrangler (2 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 611 once invoked, about $0.0004 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-31.
Other skills, from other repositories
ccal
Chinese Calendar with Lunar-Solar Conversion.
x-theme
Change terminal command line prompt theme. Globally manage the display style of all x-cmd interactive components. Supports multiple theme vendors: theme, starship, ohmyposh. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
loop
Schedule recurring tasks with notifications. Triggered by "/loop " to set up periodic monitoring.
log-work
Log the work segment that you did after the last work log until now in a.
vs-user-onboarding
Guide a brand-new SearchCLI/vs user from first-time usage questions to sign-up, purchase of Viking AI Search, AK/SK setup, and a working authenticated CLI. Use when the user says they downloaded or installed SearchCLI/vs and asks how to use it, how to start, sign up, buy, or onboard.
skill0
Root index of x-cmd skill0 sub-skills. Defines the OKR-style agent workflow (goal → rule-verified results → execute), skill discovery, and agent tooling preferences. Style: principle-first, concise, delegate specifics to authoritative external sources.