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 atman-33/workhub --skill schedule-editgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/schedule-edit)<a href="https://agentmods.dev/skills/atman-33/workhub/schedule-edit"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/schedule-edit.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.00081 | $0.02028 |
| Opus 5 | $0.00041 | $0.01014 |
| Sonnet 5 | $0.00016 | $0.00406 |
| Haiku 4.5 | $0.00008 | $0.00203 |
Grade A, and why
schedule-edit 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 4d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule Edit
Apply a natural-language instruction to one workhub schedule note by rewriting only the affected lines.
This skill is normally launched by the workhub app's Schedule tab, which passes the file path and the instruction. It also works when invoked by hand.
The file
A schedule note is Markdown with flat frontmatter and two managed sections:
---
type: schedule
title: 2026Q3 release plan
range: 2026-07-20..2026-08-31
created: 2026-07-24
updated: 2026-07-24
---
## Non-working
- weekly: sat, sun
- 2026-08-11 Mountain Day
- 2026-08-13..2026-08-15 summer leave
## Items
- [bar] I-001 2026-07-21..2026-08-07 implementation #blue task:T-0090
- [bar] I-002 2026-08-08..2026-08-19 integration test #amber
- [arrow] I-005 2026-07-21..2026-08-19 vendor lead time #gray
- [milestone] I-003 2026-08-20 release review #red
- [note] I-004 2026-07-31 monthly review 15:00
## Memo
Free-form prose. Never rewritten by this skill.
Notation
Element line:
- [<kind>] <id> <date-spec> <title> [#<color>] [task:<task-id>]
| Field | Rule |
|---|---|
<kind> |
bar, arrow, milestone, or note. No other kinds exist. |
<id> |
I- + a zero-padded number, unique in the file. Never change it. |
<date-spec> |
bar/arrow: YYYY-MM-DD..YYYY-MM-DD. milestone/note: a single YYYY-MM-DD. |
#<color> |
Optional, one of blue, green, amber, red, purple, gray. |
task:<id> |
Optional link to a task in tasks/. |
bar and arrow are the same shape of element — a span of days — and differ in
confidence: a bar is a period that is settled, an arrow is one that is still
an estimate (a vendor lead time, a buffer, work running in parallel). The app
draws the arrow as a thin double-headed line so it reads as weaker than a bar.
When an instruction asks for a period that is explicitly a guess, a buffer, or
someone else's turnaround, prefer arrow; otherwise use bar. Never change an
existing element's kind unless the instruction asks for it.
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.
- 4d ago First seen · 185 lines · 81 tokens per session scan A 53b49980137c
schedule-edit is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 2,028 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-09-03.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
shipyard-executing-plans
Use when you have a written implementation plan to execute, either in the current session with builder/reviewer agents or in a separate session with review checkpoints. Also use when the user says "build this", "implement this", "execute the plan", "run the plan", or when a plan file has been loaded with independent…
shipyard-writing-plans
Use when you have a spec, requirements, or design for a multi-step task — before touching code. Also triggers on "plan this", "break this down", "create tasks", "decompose this feature", or when a task clearly needs more than 2-3 steps to implement. If you're about to start building without a plan, or writing vague…
shipyard-handoff
Captures session context into .shipyard/HANDOFF.md so the next session can resume without losing progress.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
roadmap
An implementation plan made from a technical specification, organized into phases, milestones, and dependencies.