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 ParendumOU/Nexora --skill schedule_managegit clone --depth 1 https://github.com/ParendumOU/NexoraWrote 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/parendumou/nexora/schedule_manage)<a href="https://agentmods.dev/skills/parendumou/nexora/schedule_manage"><img src="https://agentmods.dev/badge/skills/parendumou/nexora/schedule_manage/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/parendumou/nexora/schedule_manage"><img src="https://agentmods.dev/badge/skills/parendumou/nexora/schedule_manage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00524 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
schedule_manage 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 9d 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
Schedule Management
Tool: schedule_manage. All ops use action field.
Actions
create
cron_expr (5-field) OR interval_minutes — never both.
[{"name": "schedule_manage", "args": {
"action": "create",
"name": "Daily Standup Report",
"cron_expr": "0 9 * * 1-5",
"agent_name": "my-agent",
"prompt": "Generate a short standup summary for today based on recent activity."
}}]
Cron: daily 9AM 0 9 * * * | Mon 0 9 * * 1 | weekdays 0 9 * * 1-5 | hourly 0 * * * * | 30min */30 * * * *
list
[{"name": "schedule_manage", "args": {"action": "list"}}]
get
[{"name": "schedule_manage", "args": {"action": "get", "schedule_id": "SCHEDULE_ID"}}]
update
Changed fields only.
[{"name": "schedule_manage", "args": {"action": "update", "schedule_id": "SCHEDULE_ID", "cron_expr": "0 10 * * *"}}]
activate
[{"name": "schedule_manage", "args": {"action": "activate", "schedule_id": "SCHEDULE_ID"}}]
deactivate
[{"name": "schedule_manage", "args": {"action": "deactivate", "schedule_id": "SCHEDULE_ID"}}]
trigger
Run immediately.
[{"name": "schedule_manage", "args": {"action": "trigger", "schedule_id": "SCHEDULE_ID"}}]
runs
[{"name": "schedule_manage", "args": {"action": "runs", "schedule_id": "SCHEDULE_ID"}}]
delete
Removes schedule + all run history.
[{"name": "schedule_manage", "args": {"action": "delete", "schedule_id": "SCHEDULE_ID"}}]
Notes
- Runs in background — each run = dedicated agent chat with configured prompt.
- Inactive = stored, not triggered.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 68 lines · 0 tokens per session scan A a1a3fdf5902a
schedule_manage is a skill published in the GitHub repository ParendumOU/Nexora (20 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 524 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-08-30.
Other skills, from other repositories
automation-guide
A guide for DeterminFlow Cron automations, which run agents or tasks once or on a repeating schedule.
library
A skill for managing WorkBuddy’s built-in library, which stores online documents, web links, data tables, dashboards, web pages, files, and shared spaces. It also supports publishing, collaboration, and file transfers.
background-task
Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.
agent-tool
Add a new tool/function the AI agent can call (e.g. look something up, hit an external API, perform an action). Use when extending the assistant's capabilities, wiring a new function into the agent, or when the model needs a new action. This project uses {{ cookiecutter.aiframework }}.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.