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/repair-after-a-fight)<a href="https://agentmods.dev/rules/mohitagw15856/pm-claude-skills/repair-after-a-fight"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/repair-after-a-fight/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/repair-after-a-fight"><img src="https://agentmods.dev/badge/rules/mohitagw15856/pm-claude-skills/repair-after-a-fight.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.00123 | $0.01076 |
| Opus 5 | $0.00062 | $0.00538 |
| Sonnet 5 | $0.00025 | $0.00215 |
| Haiku 4.5 | $0.00012 | $0.00108 |
Grade A, and why
repair-after-a-fight 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 13d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repair After a Fight
Every relationship has fights — what separates the strong ones isn't never fighting, it's repairing well afterward. Left unrepaired, the silence hardens and the resentment compounds. This helps you reconnect: figure out what actually needs mending, own your part specifically (not a defensive non-apology), acknowledge their hurt, and rebuild trust — because the repair is where the relationship is actually made or broken.
What This Skill Produces
- What needs repairing — separating the surface incident from the deeper hurt underneath (often "you didn't have my back" matters more than the topic)
- A genuine repair approach — owning your specific part, acknowledging their feelings, and a real (not defensive or "sorry you feel") apology where warranted
- The reopening words — how to break the silence and start the repair without reigniting the fight
- The rebuild — moving from "okay we're past it" to actually restoring trust and understanding what happened
- A both-sides note — repair usually needs each person to own their part; how to do yours without demanding theirs
Required Inputs
Ask for these if not provided:
- The fight — what it was about and what was said/done
- Your part — honestly, what you contributed (defensiveness here blocks repair)
- The relationship — partner, friend, family, and how it usually goes
- Where it stands — cold silence, a tense truce, or still raw
- Your goal — genuinely repair, or just end the standoff
Framework: Reconnect, Own, Rebuild
- Find the real hurt. The topic of the fight is often not the wound — underneath is usually feeling unheard, disrespected, or unsupported. Repair the real thing.
- Own your part specifically. A genuine "I was wrong to X, and I can see it hurt you" repairs; a defensive "I'm sorry but you..." or "sorry you feel that way" makes it worse. Take your actual part.
- Acknowledge their hurt. Show you understand how it landed for them, without rushing to defend or explain — feeling understood is most of repair.
- Reopen without reigniting. Break the silence with warmth and ownership, not a re-litigation of who was right.
- Rebuild, don't just bury. Move past "let's forget it" toward actually understanding what happened and how to handle it better — that's what restores trust.
- Do your part regardless. You can own your side without them owning theirs; leading the repair often unlocks theirs, but don't make yours conditional.
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.
- 13d ago First seen · 70 lines · 123 tokens per session scan A 42fbc8266334
repair-after-a-fight is a cursor rule published in the GitHub repository mohitagw15856/pm-claude-skills (1,357 stars, last pushed yesterday), licensed MIT. It adds 123 tokens to every session and 1,076 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-08-30.
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.