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 architectural-programme-briefgit 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/architectural-programme-brief)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/architectural-programme-brief"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/architectural-programme-brief/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/architectural-programme-brief"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/architectural-programme-brief.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.00109 | $0.01297 |
| Opus 5.5 | $0.00044 | $0.00519 |
| Sonnet 5.5 | $0.00022 | $0.00259 |
| Haiku 4.5 | $0.00011 | $0.00130 |
Grade A, and why
architectural-programme-brief 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Programme Brief
Clients brief in rooms and adjectives; buildings are designed from areas, adjacencies and constraints. The gap between the two is where scope creep lives. This converts the conversation into a schedule you can design against, tests the budget against the areas before anyone draws anything, and writes down what the project is not — the single most valuable page in any brief.
What This Skill Produces
- An accommodation schedule — every space with its area, occupancy, and the activity it must support
- Adjacency and circulation requirements — what must be near what, what must never be, and the routes between
- Site and statutory constraints — planning context, access, orientation, services, and known designations
- Performance requirements — servicing, acoustics, daylight, accessibility, and environmental targets, stated as requirements rather than aspirations
- The budget and programme reality check — the area total against the budget at a realistic rate, before design begins
- Explicit exclusions — what this project is not doing, agreed and written down
Required Inputs
Ask for these if not provided:
- The client and the driver — who they are, and what problem the building is supposed to solve
- The activities — what will actually happen in the building, by whom, and when
- The site — location, area, existing structures, access, orientation, and any known designations or constraints
- The budget and programme — the number they have and the date they need it, however soft
- The fixed points — anything already decided, promised, or non-negotiable
Framework: Activities Before Rooms, Areas Before Budget
- Brief the activity, not the room. 'A place for forty people to eat that empties in twenty minutes' designs better than 'a canteen'. Rooms are a solution; activities are the requirement.
- Put an area against everything. An unpriced schedule is a wish list. Areas are what make the budget conversation possible.
- Test the budget early and bluntly. Total area at a realistic rate per square metre, against the stated budget. If it does not work, say so in the brief rather than discovering it at tender.
- Map adjacencies as a matrix. Must-be-near, must-not-be-near, and the routes people take between them. This is where the plan actually comes from.
- Name constraints before they become surprises. Planning context, rights of light, access, ground conditions, services capacity, listed status.
- Write the exclusions down and get them agreed. The scope you did not include is only excluded if it is on paper.
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 · 87 lines · 109 tokens per session scan A 15949081125a
architectural-programme-brief is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 109 tokens to every session and 1,297 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…