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/disability-disclosure-decision)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/disability-disclosure-decision"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/disability-disclosure-decision/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/disability-disclosure-decision"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/disability-disclosure-decision.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.00124 | $0.01443 |
| Opus 5 | $0.00062 | $0.00722 |
| Sonnet 5 | $0.00025 | $0.00289 |
| Haiku 4.5 | $0.00012 | $0.00144 |
Grade A, and why
disability-disclosure-decision 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disability Disclosure Decision Skill
Whether to tell work about a disability or health condition is one of the genuinely hard modern career decisions, because both directions carry real cost: disclosing can unlock accommodations and legal protection and end the exhaustion of hiding — and can also invite bias, being passed over, or becoming "the sick one." There's no universal right answer, only the right answer for this person, condition, workplace, and moment. This skill won't tell you to disclose or not; it maps the specific tradeoffs, surfaces the options between "full disclosure" and "nothing" that people forget exist, and — if you choose to — helps you do it well.
What This Skill Produces
- A decision map for your situation: the concrete benefits and risks of disclosing here, weighted by what you'd gain (accommodations you need now? protection? relief?) and what you'd risk (this specific workplace's culture, this manager)
- The spectrum of options most people miss: not just all-or-nothing but partial and targeted disclosure — telling HR but not the team, naming the functional limitation without the diagnosis, disclosing to get an accommodation vs disclosing generally
- The timing question: application vs offer vs post-start vs point-of-need, and why each changes the calculus
- If you choose to disclose: a script tuned to the audience and the goal, and the minimum-disclosure framing (see [[accommodation-request]] for the accommodation route specifically)
Required Inputs
Ask for (if not already provided):
- The condition and what's actually driving the question (needing an accommodation now? a performance situation? tired of hiding? a new job?)
- The workplace reality, honestly: culture, this manager, whether others have disclosed and how it went, and the country's legal protections
- What the user would gain by disclosing and what they most fear
- Their own instinct — this is theirs, and the skill starts from where they lean
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 · 119 lines · 124 tokens per session scan A 21da9dbc1439
disability-disclosure-decision is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 124 tokens to every session and 1,443 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.