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 site-analysis-reportgit 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/site-analysis-report)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/site-analysis-report"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/site-analysis-report/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/site-analysis-report"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/site-analysis-report.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.00101 | $0.01356 |
| Opus 5.5 | $0.00040 | $0.00542 |
| Sonnet 5.5 | $0.00020 | $0.00271 |
| Haiku 4.5 | $0.00010 | $0.00136 |
Grade A, and why
site-analysis-report 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Analysis Report
Every expensive design change traces back to something about the site that was known but not looked at. Ground conditions, a right of way, a sewer easement, the neighbour's window. This is the systematic sweep before a line is drawn: what is there, what is allowed, what the site can hold, and which unknowns are worth paying to resolve now rather than at foundation stage.
What This Skill Produces
- Physical survey summary — topography, boundaries, existing structures, trees, ground conditions, and services
- A constraints and opportunities read — each constraint with its design consequence, and the aspects worth exploiting
- The statutory and legal position — planning designations, rights of way, easements, covenants, and party wall exposure
- Developable-capacity estimate — what the site could plausibly take, with the assumptions stated
- Orientation and environmental analysis — sun path, prevailing wind, noise sources, flood and drainage
- The risk register — the unknowns, what each could cost, and which are worth investigating before design
Required Inputs
Ask for these if not provided:
- The site — address, boundaries, area, and current use
- What surveys exist — topographical, measured building, arboricultural, ground investigation, drainage, asbestos
- The title information — registered title, easements, covenants, and rights of way if known
- The proposal, if there is one — what the client hopes to build, so capacity can be tested against it
- Local context — planning designations, neighbouring uses, access, and known local sensitivities
Framework: What Is There, What Is Allowed, What It Can Hold
- Separate the physical from the legal. A site can be perfectly buildable and legally constrained, or the reverse. Confusing the two produces schemes that die late.
- Walk the boundaries against the title plan. Fences and titles disagree more often than anyone expects, and the discrepancy is cheapest to find now.
- Find the buried constraints. Sewers, easements, and services crossing the site remove development area without appearing on any drawing.
- Convert every constraint into a design consequence. 'Protected tree' is a note; 'no foundations within 8 m of the northern boundary' is a constraint that shapes the plan.
- Test capacity with stated assumptions. A capacity figure without its assumptions is a number that will be quoted back at you.
- Price the unknowns. For each, what it might cost to be wrong, and what an investigation costs. Some are worth resolving now; say which.
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 · 90 lines · 101 tokens per session scan A bbdd9141217e
site-analysis-report is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 1,356 once invoked, about $0.0004 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…