PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-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/rules/mohitagw15856/pm-claude-skills/accessible-travel-planner)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/accessible-travel-planner"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/accessible-travel-planner/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/rules/mohitagw15856/pm-claude-skills/accessible-travel-planner"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/accessible-travel-planner.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.00114 | $0.01419 |
| Opus 5 | $0.00057 | $0.00709 |
| Sonnet 5 | $0.00023 | $0.00284 |
| Haiku 4.5 | $0.00011 | $0.00142 |
Grade A, and why
accessible-travel-planner 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 8d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessible Travel Planner Skill
Travel with a disability fails on the gap between "accessible" as a label and accessible as a reality: the "accessible" hotel room with a step to the bathroom, the airline assistance that wasn't actually booked, the wheelchair that arrives damaged, the medication held at a border. The disabled travelers who have good trips plan differently — they verify access against their specific needs rather than trusting the word, book assistance well ahead and get it in writing, and pre-plan for the predictable failures. This skill runs that planning. It can't guarantee a provider's access, so it verifies specifics with the source and builds the contingencies for when things go wrong anyway.
What This Skill Produces
- An access-verified itinerary: for each leg and stay, the specific questions to confirm against your needs (door widths, step-free routes, roll-in shower, bed height, hearing/vision provisions) — because "accessible" means different things
- An assistance-booking checklist: flight/rail/transfer assistance booked in advance with the deadlines, confirmations in writing, and what to reconfirm and when
- An equipment & medication plan: protecting mobility equipment in transit, battery/wheelchair airline rules, carrying medication across borders, and backups
- Contingency scripts: for the assistance that doesn't show, the damaged equipment, the room that isn't as described — what to say and to whom, in the moment
Required Inputs
Ask for (if not already provided):
- The trip (where, when, how — flying/rail/road) and the specific access needs (mobility aid used, transfer ability, sensory needs, medical equipment, fatigue/ pacing, service animal)
- The bookings made or being considered (airline, hotels, transfers) so they can be access-checked
- Equipment and medication involved, and any documentation the user has (medical letters, equipment specs)
- Risk tolerance and support: solo or with a companion, and how much buffer they want
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.
- 8d ago First seen · 118 lines · 114 tokens per session scan A 3ef5a1c3c599
accessible-travel-planner is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 1,419 once invoked, about $0.0006 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 cursor rules, from other repositories
cursor
Always-on my-adhd-caveman. Off with "stop adhd-caveman" or "normal mode".
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.