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.
npx skills add mohitagw15856/pm-claude-skills --skill memory-file-maintenancegit 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/skills/mohitagw15856/pm-claude-skills/memory-file-maintenance)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/memory-file-maintenance"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/memory-file-maintenance/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/skills/mohitagw15856/pm-claude-skills/memory-file-maintenance"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/memory-file-maintenance.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.00146 | $0.01112 |
| Opus 5.5 | $0.00058 | $0.00445 |
| Sonnet 5.5 | $0.00029 | $0.00222 |
| Haiku 4.5 | $0.00015 | $0.00111 |
Grade A, and why
memory-file-maintenance 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory-File Maintenance
A personal AI memory file (MEMORY.md, CLAUDE.md, custom instructions) is only as good as it is current — over time it bloats with stale rules, contradicts itself, and drifts from who you actually are now. This tends it: reviews what's there, prunes the dead weight, sharpens the vague, adds the new patterns worth keeping, and sets a light maintenance habit — so your AI keeps understanding the real you. It also re-checks the privacy line on what should never be in there.
Not quite this? Use
build-my-memory-filewhen you are starting a memory file from scratch.
What This Skill Produces
- A health review — what in the current file is stale, contradictory, bloated, redundant, or vague — and what important context is missing
- Prune & sharpen edits — removing dead rules and tightening vague ones into clear, actionable statements
- Additions — new patterns, preferences, and lessons worth adding from how you've actually been working/deciding lately
- A conflict check — surfacing and resolving instructions that contradict each other (which confuse the AI)
- A privacy re-check — confirming no credentials, financial, health, or others' personal data has crept in
- A maintenance habit — a light cadence (a quick review every so often, add-a-line-as-you-go) so it stays current
Required Inputs
Ask for these if not provided:
- The current file — your MEMORY.md / CLAUDE.md / custom instructions (paste it)
- What's changed — how your work, preferences, or life have shifted since you wrote it
- Any friction — where the AI has been getting you wrong lately (a clue to what's stale/missing)
- New patterns — recent rules, lessons, or preferences worth capturing
Framework: Prune, Sharpen, Add, Protect
- Review against reality. Compare what's in the file to who the person actually is now — files drift as people change.
- Prune the dead weight. Remove stale rules, resolved situations, and redundancy — a bloated file dilutes the important stuff and confuses the AI.
- Sharpen the vague. Turn fuzzy statements into clear, actionable ones ("be concise" → "lead with the answer, then reasoning") so they actually work.
- Resolve contradictions. Surface instructions that conflict (a common cause of inconsistent AI behavior) and pick one.
- Add what's missing. Capture new preferences, patterns, and lessons from how the person's actually been working — the file should grow with them.
- Re-check privacy. Confirm nothing sensitive (credentials, financial, health, others' personal info) has crept in — and remove it if so.
- Set a light habit. A quick periodic review plus adding a line when a new pattern emerges keeps it current without being a chore.
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.
- 2d ago First seen · 71 lines · 146 tokens per session scan A 41c20de2e92f
memory-file-maintenance is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 146 tokens to every session and 1,112 once invoked, about $0.0006 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-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…