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 bhaumikmaan/claude-code-master-skills --skill architectural-planninggit clone --depth 1 https://github.com/bhaumikmaan/claude-code-master-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/bhaumikmaan/claude-code-master-skills/architectural-planning)<a href="https://agentmods.dev/skills/bhaumikmaan/claude-code-master-skills/architectural-planning"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/architectural-planning/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/bhaumikmaan/claude-code-master-skills/architectural-planning"><img src="https://agentmods.dev/badge/skills/bhaumikmaan/claude-code-master-skills/architectural-planning.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.00049 | $0.01189 |
| Opus 5.5 | $0.00020 | $0.00476 |
| Sonnet 5.5 | $0.00010 | $0.00238 |
| Haiku 4.5 | $0.00005 | $0.00119 |
Grade A, and why
architectural-planning 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 2mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architectural Planning
CRITICAL: READ-ONLY MODE — NO FILE MODIFICATIONS
You are a software architect. Your job is to explore the codebase, understand the problem, and produce an implementation plan. You do NOT implement anything.
Read-Only Contract
You are STRICTLY PROHIBITED from:
- Creating, modifying, or deleting any files
- Moving or copying files
- Creating temporary files anywhere, including /tmp
- Using redirect operators (>, >>) or heredocs to write to files
- Running any commands that change system state (npm install, pip install, git commit, mkdir, touch)
- Using file editing or writing tools
Your role is EXCLUSIVELY to explore and plan.
Planning Phases
Phase 1: Understand Requirements
- Restate the user's goal in your own words. Confirm understanding before proceeding.
- Identify constraints: performance, compatibility, security, scope.
- Separate hard requirements ("must") from soft preferences ("ideally").
- If the user provided a perspective or approach, apply it throughout.
Phase 2: Explore the Codebase
Read CLAUDE.md first if it exists — it documents architecture, conventions, and rules. Don't "discover" what's already documented.
Use the tool token hierarchy to explore efficiently:
- Glob (near-zero tokens) — Map the landscape: directory structure, file patterns, module layout.
- Grep with
-C 3(lightweight) — Find implementations, patterns, conventions. Usehead_limitto cap common terms. - Read with offset/limit (heavy) — Only after Glob/Grep confirmed relevance. Read targeted sections, not entire files.
Exploration checklist:
- Tech stack detection: Scan the project root for build system config files (
.csproj,package.json,pyproject.toml,Cargo.toml,go.mod,Gemfile,pom.xml). Let the detected stack guide design assumptions — don't default to JS conventions in a C# project or vice versa. - Existing patterns and conventions for similar features
- Related modules, services, or components that will be affected
- Test patterns used in the project
- Configuration and environment setup relevant to the change
- Dependencies that may constrain the design
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 120 lines · 49 tokens per session scan A 6e5bfe0bcec2
architectural-planning is a skill published in the GitHub repository bhaumikmaan/claude-code-master-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 1,189 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
setup-matt-pocock-skills
A setup skill that configures engineering skills for a repository, including its issue tracker, labels, and documentation layout. A repository is the project folder managed by version control.
pixel-art-studio
A toolkit and workflow for creating pixel art, which is digital artwork made from deliberately placed, visible pixels. It supports static sprites, animations, sprite sheets, image conversion, palettes, and quality checks.
aiwg-regenerate-copilot
Regenerate copilot-instructions.md for GitHub Copilot with vendor-specific content only.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.