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 OctoPerf/octoperf-claude-plugins --skill octoperf-schedulinggit clone --depth 1 https://github.com/OctoPerf/octoperf-claude-pluginsWrote 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/octoperf/octoperf-claude-plugins/octoperf-scheduling)<a href="https://agentmods.dev/skills/octoperf/octoperf-claude-plugins/octoperf-scheduling"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-scheduling/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/octoperf/octoperf-claude-plugins/octoperf-scheduling"><img src="https://agentmods.dev/badge/skills/octoperf/octoperf-claude-plugins/octoperf-scheduling.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.00141 | $0.01974 |
| Opus 5 | $0.00071 | $0.00987 |
| Sonnet 5 | $0.00028 | $0.00395 |
| Haiku 4.5 | $0.00014 | $0.00197 |
Grade A, and why
octoperf-scheduling 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 12d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OctoPerf — Scheduling scenarios
OctoPerf can fire a load-test scenario on a schedule — either once at
a future moment, or recurrently via a cron expression. Every fire
consumes credits exactly like a manual run_scenario, so a daily
cron drains the subscription every day until you pause or delete it.
When this applies
- The user wants a scenario to run automatically — overnight batch, weekly soak test, regression run after a release tag, etc.
- The user is asking about an existing scheduled job — show it, pause it, change its cadence, delete it.
The pitfalls — read this BEFORE invoking any schedule tool
1. The cron format is Unix 5-field, not Quartz, and it's in UTC
OctoPerf's cron parser is UnixCronTrigger — 5 fields, no seconds,
evaluated in UTC on the server. Quartz expressions like
0 0 3 * * ? (6 fields) are rejected with an opaque HTTP 400.
The five fields are:
minute hour day-of-month month day-of-week
0-59 0-23 1-31 1-12 0-7 (0 and 7 are Sunday)
Use * for "any value". Comma lists (1,15), ranges (1-5) and step
values (*/15) work. Day-of-week uses Unix conventions (1=Monday in
the documented examples).
2. UTC, not local time — convert explicitly
A user saying "every night at midnight" almost never means UTC. You have to convert their local time to UTC before computing the expression. Examples for Europe/Paris:
| User's local cadence | DST (CEST = UTC+2) | Winter (CET = UTC+1) |
|---|---|---|
| Daily at midnight Paris | 0 22 * * * |
0 23 * * * |
| Daily at 09:00 Paris | 0 7 * * * |
0 8 * * * |
| Weekdays at 08:30 Paris | 30 6 * * 1-5 |
30 7 * * 1-5 |
| Monthly on the 1st at 03:00 Paris | 0 1 1 * * |
0 2 1 * * |
Daylight Saving Time is a real concern: a daily Paris cron set in summer will fire one hour off in winter (and vice versa). The user either accepts that drift, or you advise picking a less DST-sensitive slot (e.g. anchor on UTC and tell them when it fires in local time).
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.
- 12d ago First seen · 166 lines · 141 tokens per session scan A 9d6b0986efdc
octoperf-scheduling is a skill published in the GitHub repository OctoPerf/octoperf-claude-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 141 tokens to every session and 1,974 once invoked, about $0.0007 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
forge-app-review
Performs a lightweight pre-release readiness review of Atlassian Forge apps across manifest/module wiring, architecture, runtime compatibility, dependency posture, tests, deploy readiness, and obvious security, cost, or reliability smells. Use when the user asks "review my Forge app", "pre-deploy check", "is this app…
run-iteration-eval
Run the Logic-Lens content-eval pipeline for one iteration and produce a scored summary.json — use to measure a skill change. Wraps scripts/run-content-evals.sh (runner, costs tokens) and scripts/grade-iteration.py (grader, free, re-runnable). ALWAYS sync the plugin cache first. Use when the user wants to "run the…
spec-driven-dev
Use when starting any non-trivial feature, refactor, or new project that will touch more than one file. Drives an AI coding agent through a gated Spec → Plan → Build → Test → Review → Ship lifecycle so work is specified before it is built, verified before it is reviewed, and reviewed before it ships.
iterate-skill
Run the Logic-Lens skill-improvement loop end to end — baseline → diagnose failures → edit → sync cache → re-eval → verify net gain → iterate until clean. Use whenever the goal is to RAISE a skill's eval score or fix a failing eval mode: "improve logic-review", "the format compliance is failing, fix it", "iterate on…
sumup-testing
Set up and run SumUp sandbox tests. Use when configuring a SumUp test merchant, picking test cards, triggering deliberate failure (amount = 11), or building a SumUp end-to-end test harness.
python-testing
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.