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 vibesurf-ai/claude-surf --skill config-schedulegit clone --depth 1 https://github.com/vibesurf-ai/claude-surfWrote 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/vibesurf-ai/claude-surf/config-schedule)<a href="https://agentmods.dev/skills/vibesurf-ai/claude-surf/config-schedule"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/config-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/skills/vibesurf-ai/claude-surf/config-schedule"><img src="https://agentmods.dev/badge/skills/vibesurf-ai/claude-surf/config-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.00032 | $0.00737 |
| Opus 5 | $0.00016 | $0.00368 |
| Sonnet 5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
config-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 11d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Schedule - Workflow Schedule Management
Overview
Manage scheduled workflow executions using cron expressions. Schedule workflows to run automatically at specified times.
When to Use
- User wants to schedule a workflow to run automatically
- User needs to set up cron-based workflow triggers
- User wants to enable/disable existing schedules
- User needs to view or update workflow schedules
- User wants to see which workflows have schedules configured
API Endpoints
Base path: $VIBESURF_ENDPOINT/api/schedule
Schedule Management
| Action | Method | Endpoint | Description |
|---|---|---|---|
| List Schedules | GET | /api/schedule |
Get all workflow schedules |
| Get Schedule | GET | /api/schedule/{flow_id} |
Get schedule for specific workflow |
| Create Schedule | POST | /api/schedule |
Create new schedule for a workflow |
| Update Schedule | PUT | /api/schedule/{flow_id} |
Update existing schedule |
Request Examples
Create Schedule
POST /api/schedule
{
"flow_id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"cron_expression": "0 9 * * 1-5",
"is_enabled": true,
"description": "Run every weekday at 9 AM"
}
Update Schedule
PUT /api/schedule/{flow_id}
{
"cron_expression": "0 12 * * *",
"is_enabled": true,
"description": "Run daily at noon"
}
Enable/Disable Schedule
PUT /api/schedule/{flow_id}
{
"is_enabled": false
}
Schedule Fields
| Field | Type | Required | Description |
|---|---|---|---|
| flow_id | string | Yes | Workflow/Flow ID to schedule |
| cron_expression | string | No | Cron expression (e.g., '0 9 * * 1-5') |
| is_enabled | bool | No | Whether the schedule is active |
| description | string | No | Description of the schedule |
Cron Expression Format
Standard cron format: minute hour day_of_month month day_of_week
| Expression | Description |
|---|---|
0 9 * * 1-5 |
Every weekday at 9:00 AM |
0 12 * * * |
Every day at 12:00 PM |
0 */6 * * * |
Every 6 hours |
0 0 * * 0 |
Every Sunday at midnight |
0 8,20 * * * |
At 8:00 AM and 8:00 PM daily |
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.
- 11d ago First seen · 98 lines · 32 tokens per session scan A 73a1bb5a940b
config-schedule is a skill published in the GitHub repository vibesurf-ai/claude-surf (24 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 737 once invoked, about $0.0002 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
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
memstack-business-client-onboarding
Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.
memstack-product-roadmap-builder
Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.
memstack-product-user-story-generator
Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.