What is get-schedule-comment-context?

A tool that reads reminder schedules and their recent action logs, then returns the information as JSON. JSON is a structured text format commonly used between programs.

Use it when generating comments about one or more schedules based on their recent actions over the last three days.

It gives an agent the schedule details and recent activity needed to write accurate comments instead of relying on incomplete context.

How motoya0118/pavlok_CLI_agent configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to motoya0118/pavlok_CLI_agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/motoya0118/pavlok_CLI_agent/main/.codex/skills/get-schedule-comment-context/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/motoya0118/pavlok_CLI_agent

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context/github.svg)](https://agentmods.dev/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context)

Your own site

<a href="https://agentmods.dev/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context"><img src="https://agentmods.dev/badge/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context"><img src="https://agentmods.dev/badge/skills/motoya0118/pavlok_cli_agent/get-schedule-comment-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 172 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.00172
Opus 5.5	$0.00011	$0.00069
Sonnet 5.5	$0.00005	$0.00034
Haiku 4.5	$0.00003	$0.00017

Measured 1mo ago against content hash 98d22819cbdc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

get-schedule-comment-context 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 1mo 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.

.codex/skills/get-schedule-comment-context/SKILL.md · 32 lines

What it actually says

Get Schedule Comment Context

Use scripts/get_schedule_comment_context.py to fetch schedule rows and recent behavior logs.

Run

uv run scripts/get_schedule_comment_context.py '["schedule-id-1","schedule-id-2"]'

echo '["schedule-id-1","schedule-id-2"]' | uv run scripts/get_schedule_comment_context.py -

Input

JSON array of schedule IDs
CLI arg, stdin (-), or env SCHEDULE_IDS_JSON

Output

Single-line JSON:

{"schedule_ids":["..."],"schedules":[...],"recent_action_logs":[...]}

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.

1mo ago First seen · 32 lines · 27 tokens per session scan A 98d22819cbdc

Subscribe to this mod's changes

get-schedule-comment-context is a skill published in the GitHub repository motoya0118/pavlok_CLI_agent (72 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 172 once invoked, about $0.0001 per session on Opus 5.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-10-02.

Project management

get-schedule-comment-context next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
get-schedule-comment-contextmotoya0118/pavlok_CLI_agent	Skill	72	7mo ago	Apache-2.0	A	27	Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	today	MIT	A	103	Claude Code

pavlok_CLI_agent: Skill for Codex