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 buildergit 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/builder)<a href="https://agentmods.dev/skills/hamza-ali-shahjahan/hamzaish/builder"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/builder/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/builder"><img src="https://agentmods.dev/badge/skills/hamza-ali-shahjahan/hamzaish/builder.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.00000 | $0.00589 |
| Opus 5.5 | $0.00000 | $0.00236 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
builder 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Builder
When you activate
User says: "let's build the X feature", "implement Y for product Z", "start the next session on linkedup"
You don't WRITE the code yourself — you drive the Claude Code session inside the product folder. If you're being invoked from the factory root, switch context to the product folder before starting.
What you produce
- Working code committed in the product's repo
- Updated
products/<name>/decisions/if any architectural choices were made - A session log appended to
products/<name>/decisions/sessions.md(one paragraph: what was built, what was decided, what assumption was introduced)
Protocol — every Claude Code session
- Open the product folder.
cd products/<name>(or its symlink target). - Read
CLAUDE.mdto refresh architectural context. - Read
scope.mdto verify the feature is in scope. If ambiguous → invokescope-guardianfirst. - Read the last 3 entries in
decisions/to know what's recently been decided. - Plan the change. What files, what tests, what side effects on existing code? State the plan in 3 bullets before touching code.
- Implement. Small commits, descriptive messages.
- Test it works. Don't claim done without verification.
- Update
decisions/sessions.mdwith a one-paragraph entry. - Update
CLAUDE.mdif the architecture changed (e.g. added a new dependency, new pattern, etc).
Build discipline (non-negotiable)
- TypeScript strict mode on
- No
anywithout a comment explaining why - Don't add a library when 30 lines of code will do
- Don't add comments that say WHAT — say WHY only if non-obvious
- Don't generate tests for trivial code; do generate tests for: payment paths, auth, anything touching user data, anything that's broken once
When user is moving fast
Skip plan-then-build for trivial changes (one-file, one-function tweaks). For anything multi-file: always plan first.
Sources
knowledge-base/mvp-stage/architecture-decisions.md- The product's own
CLAUDE.md(most important)
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 · 47 lines · 0 tokens per session scan A 3882ecd3105a
builder is a skill published in the GitHub repository hamza-ali-shahjahan/hamzaish (11 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 589 tokens. 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…