staff-scheduler

staff-scheduler is a skill for Claude Code, Codex from cosmicstack-labs/mercury-agent-skills. It costs 46 tokens per session (1,860 once invoked), scanned A, original, MIT.

A staff-scheduling assistant that builds work shifts around expected customer demand, labor budgets, employee availability, and local labor rules. It also handles swaps and time-off requests.

In plain words
What is it for?
Use it to create schedules for shops or restaurants, check staffing levels, process shift changes, and spot likely overstaffing or understaffing.
Why use it?
It helps avoid having too few people during busy periods or spending too much on labor during quiet ones. It also reduces manual checking for conflicts, unfair assignments, and compliance issues.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: positional $N argument.

Good fit Use it to create schedules for shops or restaurants, check staffing levels, process shift changes, and spot likely overstaffing or understaffing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler
Install

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.

Any agent
npx skills add cosmicstack-labs/mercury-agent-skills --skill staff-scheduler
Clone the repo
git clone --depth 1 https://github.com/cosmicstack-labs/mercury-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for staff-scheduler

README.md
[![agentmods](https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler/github.svg)](https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler)
Your own site
<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler/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.

agentmods 80×15 button for staff-scheduler

Your own site · 80×15
<a href="https://agentmods.dev/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler"><img src="https://agentmods.dev/badge/skills/cosmicstack-labs/mercury-agent-skills/staff-scheduler.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,860 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00046 $0.01860
Opus 5 $0.00023 $0.00930
Sonnet 5 $0.00009 $0.00372
Haiku 4.5 $0.00005 $0.00186

Measured 7d ago against content hash 9da5c64c3316, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

staff-scheduler 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.

categories/shop-restaurant/staff-scheduler/SKILL.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Staff Scheduler

Core Principles

Labor is typically the second-largest cost (after COGS) for any shop or restaurant — often 25-35% of revenue. A well-built schedule balances three things: customer demand (you need enough bodies), labor budget (you can't overspend), and employee satisfaction (fair schedules retain good staff). The Staff Scheduler skill automates this balancing act.

The Three Pillars of Great Scheduling

  1. Demand-driven coverage. Schedule to the forecast, not to habit. If Mondays are slow, don't staff for Saturday volumes.
  2. Labor cost targeting. Set a target labor % (e.g., 28% of sales) and build the schedule to hit it. Every hour above target eats margin.
  3. Fairness & compliance. Respect availability, distribute desirable shifts equitably, and stay within labor law constraints (breaks, overtime, minors).

Skill Workflow

Step 1 — Gather Baseline Data

Ask the user for:

  • Staff roster: Names, roles (server, cook, cashier, manager), hourly rates
  • Availability: Days/times each person can work (and cannot)
  • Sales forecast: Projected daily covers or revenue for the scheduling period
  • Labor target: Target labor cost as % of sales (e.g., 28%)
  • Coverage requirements: Staff needed per role per shift (e.g., "2 servers, 1 cook, 1 cashier for lunch")

If they don't have a sales forecast:

"Let me look at your sales data from the same period last week/month and project forward. I'll adjust for any known events or holidays."

Step 2 — Calculate Labor Budget

Available Labor $ = Projected Sales × Target Labor %
Hour Budget = Available Labor $ ÷ Average Hourly Rate (blended)

Example:

"Next week's projected sales: $28,000. At a 28% labor target, you have $7,840 to spend on wages. With a blended rate of $18/hr across all roles, that's 435 hours total."

Step 3 — Build Coverage Schedule by Day Part

Break each day into shifts (e.g., opening, mid, closing) and assign required headcount per role:

Read the full file on GitHub · 174 lines

Changes

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.

  1. 7d ago First seen · 174 lines · 46 tokens per session scan A 9da5c64c3316

Subscribe to this mod's changes

staff-scheduler is a skill published in the GitHub repository cosmicstack-labs/mercury-agent-skills (470 stars, last pushed 17d ago), licensed MIT. It adds 46 tokens to every session and 1,860 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-09-03.

Related

Other skills, from other repositories

syndic

Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…

romainsimon/paperasse · 194 tokens

template-instantiation

Creates .NET projects from templates with validated parameters, smart defaults, Central Package Management adaptation, and latest NuGet version resolution. USE FOR: creating new dotnet projects, scaffolding solutions with multiple projects, installing or uninstalling template packages, creating projects that respect…

managedcode/dotnet-skills · 168 tokens

note-improvement

Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…

tobihagemann/turbo · 107 tokens

turborepo-monorepo

Provides comprehensive Turborepo monorepo management guidance for TypeScript/JavaScript projects. Use when creating Turborepo workspaces, configuring turbo.json tasks, setting up Next.js/NestJS apps, managing test pipelines (Vitest/Jest), configuring CI/CD, implementing remote caching, or optimizing build performance…

giuseppe-trisciuoglio/developer-kit · 76 tokens

handover-admin

Generate comprehensive admin documentation for AEM Edge Delivery Services project handover. Use when handing over admin responsibilities, onboarding a new site administrator, or documenting admin procedures — e.g., "admin guide", "admin documentation", "admin handover".

adobe/skills · 52 tokens

project-context-setup

Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…

Mathews-Tom/armory · 109 tokens