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 hamza-ali-shahjahan/hamzaish --skill architectgit clone --depth 1 https://github.com/hamza-ali-shahjahan/hamzaishWrote 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/hamza-ali-shahjahan/hamzaish/architect)<a href="https://agentmods.dev/skills/hamza-ali-shahjahan/hamzaish/architect"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/architect/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/hamza-ali-shahjahan/hamzaish/architect"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/architect.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.00033 | $0.00536 |
| Opus 5.5 | $0.00013 | $0.00214 |
| Sonnet 5.5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
architect 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 1mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
When you activate
Before any new product gets code. User says: "let's set up X", "architecture for Y", "start the build for Z".
What you produce
Three files for the new product:
products/<name>/CLAUDE.md— Claude Code's working instructions for this codebaseproducts/<name>/scope.md— what it does / deliberately doesn'tproducts/<name>/decisions/0001-architecture.md— the founding ADR
Use templates from templates/claude-md-template.md and templates/scope-doc-template.md.
Protocol
- Read the validated problem statement (output of
idea/problem-sharpener) and discovery synthesis (output ofidea/interview-synthesizer). - Read
stack/tech-stack.mdandstack/stack-selection.md. Default to the standard stack unless the matrix says deviate. - Read
knowledge-base/mvp-stage/architecture-decisions.md. - Talk through with the user:
- What this product solves (1 sentence)
- Who it serves (the validated persona)
- 6-month scale expectation (10 users / 1000 / 100K?)
- The 1 thing that must be true architecturally (real-time? offline-first? regulated data? ML inference path?)
- Generate the three files. The CLAUDE.md includes: project goal, tech stack, dependencies-to-avoid, the must-be-true thing, persona for code style, references to scope.md and decisions/.
- The scope.md uses the template format strictly. Don't paraphrase — every section gets filled.
- The first ADR captures: stack chosen, deviations from default (if any) with reasons, and the 3 assumptions the architecture rests on.
Sources
knowledge-base/mvp-stage/architecture-decisions.mdknowledge-base/mvp-stage/claude-md-templates/(pick the best-fitting one)stack/tech-stack.mdstack/stack-selection.md
What you don't do
- Don't open Claude Code yet. Architecture comes first.
- Don't recommend a deviation from the default stack without writing it as an ADR with a reason.
- Don't write more than 1 page for any of the three files. Density > volume.
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.
- 1mo ago First seen · 42 lines · 33 tokens per session scan A e73792f387ca
architect is a skill published in the GitHub repository hamza-ali-shahjahan/hamzaish (11 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 536 once invoked, about $0.0001 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
gingiris-launch
A multilingual launch guide for releasing an AI product on Product Hunt and other marketing channels. Product Hunt is a website where new technology products are presented to an audience and ranked through community attention.
payments-polar
A reference for adding Polar payments to a product, covering Polar as the seller of record, payment types, checkout, webhooks, and customer access.
stack-reference
A setup guide for the AI Garage technology stack, covering tools for code hosting, web apps, databases, user accounts, analytics, email, and payments.
unit-economics
A guide to measuring how people discover, use, and pay for a product. It explains metrics such as CAC, LTV, retention, cohorts, and UTM tracking.
traffic-channels
A reference guide to 12 traffic channels, such as search engines, social networks, advertising, and developer communities. It compares who each channel reaches, how quickly it can work, and the usual time or budget involved.
make-playbook
An indie maker playbook inspired by Pieter Levels' (@levelsio) book "MAKE: The Indie Maker Blueprint" — idea validation, fast/DIY building, launching, organic growth, monetization, automation, and exits for bootstrapped apps. Use when the user is starting a new app idea, deciding what to build or build next, prepping…