pto-planning

pto-planning is a skill for Claude Code, Codex from awslabs/agentcore-samples. It costs 21 tokens per session (278 once invoked), scanned A, original, Apache-2.0.

A paid-time-off assistant that checks an employee’s remaining leave, explains the relevant workplace policy, and can submit a request.

In plain words
What is it for?
Use it to review PTO availability, understand time-off requirements, plan dates, or submit a request when the employee ID and dates are provided.
Why use it?
It avoids checking balances and policy documents manually, while reducing the risk of requesting unavailable time off or missing notice and rollover rules.

Skill for Claude CodeCodex

About the project

Amazon Bedrock AgentCore Samples is a collection of examples and tutorials for deploying and operating AI agents with Amazon Bedrock AgentCore. Developers use it to integrate agent applications built with different frameworks and language models while learning AgentCore features. The catalogue add-ons provide agent-oriented guidance for working with these samples and services.

awslabs/agentcore-samples · 3,335 stars · on GitHub

Install

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.

agentmods
npx agentmods add skills/awslabs/agentcore-samples/pto-planning
Any agent
npx skills add awslabs/agentcore-samples --skill pto-planning
Clone the repo
git clone --depth 1 https://github.com/awslabs/agentcore-samples

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

agentmods badge for pto-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/awslabs/agentcore-samples/pto-planning.svg)](https://agentmods.dev/skills/awslabs/agentcore-samples/pto-planning)
Your own site
<a href="https://agentmods.dev/skills/awslabs/agentcore-samples/pto-planning"><img src="https://agentmods.dev/badge/skills/awslabs/agentcore-samples/pto-planning.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 278 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.00278
Opus 5 $0.00010 $0.00139
Sonnet 5 $0.00004 $0.00056
Haiku 4.5 $0.00002 $0.00028

Measured 5d ago against content hash 7595ac803529, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pto-planning 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 5d 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.

01-features/06-observe-evaluate-optimize-your-agent/02-evaluate/skills-evaluation/skills/pto-planning/SKILL.md · 31 lines

What it actually says

PTO Planning Instructions

Use this skill when an employee asks to check, plan, or submit paid time off.

Required workflow

  1. Identify the employee ID and whether the request is informational or asks for a submission.
  2. Call get_pto_balance for the employee before making any recommendation.
  3. Call lookup_hr_policy with topic="pto" and explain the relevant notice and rollover rules.
  4. If the user explicitly asks to submit time off and provides both dates:
    • Confirm that the balance is available.
    • Call submit_pto_request with the employee ID, start date, end date, and the user's reason when provided.
  5. If required information is missing, ask for it instead of inventing values or submitting a request.
  6. Return a concise PTO Planning Summary containing:
    • Employee ID
    • Remaining PTO balance
    • Relevant policy requirements
    • Requested dates, when supplied
    • Submission status and request ID, when submitted

Never claim that a request was submitted unless submit_pto_request returned a successful result.

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.

  1. 5d ago First seen · 31 lines · 21 tokens per session scan A 7595ac803529

Subscribe to this mod's changes

pto-planning is a skill published in the GitHub repository awslabs/agentcore-samples (3,335 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 278 once invoked, about $0.0001 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-30.