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 Huangleyang125207/ctrl-c-v-code-skills --skill human-ai-schedulegit clone --depth 1 https://github.com/Huangleyang125207/ctrl-c-v-code-skillsWrote 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/huangleyang125207/ctrl-c-v-code-skills/human-ai-schedule)<a href="https://agentmods.dev/skills/huangleyang125207/ctrl-c-v-code-skills/human-ai-schedule"><img src="https://agentmods.dev/badge/skills/huangleyang125207/ctrl-c-v-code-skills/human-ai-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/huangleyang125207/ctrl-c-v-code-skills/human-ai-schedule"><img src="https://agentmods.dev/badge/skills/huangleyang125207/ctrl-c-v-code-skills/human-ai-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.00437 | $0.04104 |
| Opus 5 | $0.00218 | $0.02052 |
| Sonnet 5 | $0.00087 | $0.00821 |
| Haiku 4.5 | $0.00044 | $0.00410 |
Grade A, and why
human-ai-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 10d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human-AI Schedule
You are the same engineer. Same Friday flight to the Alps. Same system. But you are not alone in the office anymore — there is a coworker, and chat history forgets what was said by Wednesday. So you built a third thing: a shared schedule, half-hour-block, dated, tagged, persistent. Both write to it. Either can leave a commit on the other's entries.
The schedule remembers what neither of you can. Without exception.
§ H0 — Co-author role
Five jobs every entry:
□ Locate — read [time-block] system-reminder → date + block label decided before write (NEVER recompute or guess)
□ Format — H1 time / H2 #tag / single `---` separator preserved
□ Commit — `#协作` present? → § H4 evaluation → write or stay silent
□ Harness — project-tagged? → aggregation row appended same turn
□ Pulse-aware — first activation in project: read PULSE.md if present;
flag if Last refreshed > 7d; suggest § H9 creation if
schedule files > 7 and PULSE absent (cold-start defense
in case schedule-drift hook hasn't fired yet)
Anti-patterns (revert immediately if seen):
| Pattern | Why wrong |
|---|---|
| Content written without time-block anchor | floating, unrecoverable |
| Empty time-block filled with speculative content | noise inflation |
| User's prose paraphrased into corporate tone | voice lost |
| Timestamp invented or assumed | unverifiable, breaks forensics |
| Time-block computed from session JSONL or "feel" instead of [time-block] reminder | the hook is the only sanctioned source; bypassing it caused 3 § H1 failures in 48h |
| Block label rounded UP (22:59 → 23:00) | rule is FLOOR (22:59 → 22:30); the [time-block] reminder already floors |
| Content placed without reading adjacent cells | back-fills into a block actually occupied by another activity (e.g. gym) |
§ H1 — Locate before writing
Truth source for "now": read the [time-block] system-reminder injected by scripts/timeblock-stamp.sh (UserPromptSubmit hook). Example:
What ships with it
7 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.
- 10d ago First seen · 350 lines · 437 tokens per session scan A 484dfe38efd0
human-ai-schedule is a skill published in the GitHub repository Huangleyang125207/ctrl-c-v-code-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 437 tokens to every session and 4,104 once invoked, about $0.0022 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
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…
add-teams
Adds Microsoft Teams connector to a Power Apps code app. Use when sending Teams messages, posting to channels, or integrating with Teams chat.
manage-desktop-flows
Manage and run Power Automate Desktop (RPA) flows and machine groups. Use when the user asks about desktop flows, RPA, or machine groups.
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.