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/schedule-recipe)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/schedule-recipe"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/schedule-recipe/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/schedule-recipe"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/schedule-recipe.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.00090 | $0.01047 |
| Opus 5 | $0.00045 | $0.00524 |
| Sonnet 5 | $0.00018 | $0.00209 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
schedule-recipe 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule Recipe Skill
Convert a recurring intent — "competitive briefing every Monday 8am" — into the concrete, copy-paste setup for whatever runner the user actually has, with failure handling so it degrades loudly, not silently.
What This Skill Produces
- A runner recommendation (or confirmation of the user's choice) with the reason
- The exact setup — command, cron expression, or workflow file — ready to paste
- The run prompt: what the scheduled agent should do each cycle, including which skill to load
- Failure alerting and a first-run test plan
Required Inputs
Ask for (if not already provided):
- What should run — which skill or task, and what inputs it reads each cycle
- Cadence and timezone — "every Friday 4pm" means nothing without one
- Where it can run — Claude Code (routines/loops), a server with cron, n8n, or GitHub Actions
- Where the output should land — file in a repo, Slack/email, a Brain folder, a PR
Runner Selection
Pick the simplest runner the user already has, in this order:
| Runner | Choose when | Setup shape |
|---|---|---|
Claude Code routine (/schedule) |
The user lives in Claude Code and the task needs an agent (reads repos, runs skills) | A scheduled cloud agent with the run prompt |
Claude Code /loop |
Same-session polling or short-lived recurrence, not a standing schedule | /loop <interval> <command> |
| GitHub Actions cron | Inputs and output both live in a repo; team wants runs versioned and reviewable | A workflow YAML with schedule: trigger |
| n8n / Make | The trigger or output is a SaaS app (Slack, CRM, sheets) | A workflow calling the skills REST API |
| System cron | A server exists and the task is a script | A crontab line invoking the CLI |
State the choice and the runner-up. If the user names a runner, use it — don't relitigate.
The Run Prompt
Every recipe includes the prompt the scheduled run executes. It must contain:
- The skill to load and the artifact to produce
- The sources to read this cycle — explicit paths/URLs, not "the usual"
- Where to write the result and how to mark the edition (date, sources read)
- What to do on missing sources — name the failure behaviour, never fabricate
- Delta instruction if recurring: read the previous edition first and report changes (see
delta-briefing)
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 · 82 lines · 90 tokens per session scan A 804058cb0cbd
schedule-recipe is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,352 stars, last pushed 3d ago), licensed MIT. It adds 90 tokens to every session and 1,047 once invoked, about $0.0005 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.