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.
git 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/commands/hamza-ali-shahjahan/hamzaish/goal)<a href="https://agentmods.dev/commands/hamza-ali-shahjahan/hamzaish/goal"><img src="https://agentmods.dev/badge/commands/hamza-ali-shahjahan/hamzaish/goal/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/commands/hamza-ali-shahjahan/hamzaish/goal"><img src="https://agentmods.dev/badge/commands/hamza-ali-shahjahan/hamzaish/goal.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.00074 | $0.01685 |
| Opus 5 | $0.00037 | $0.00843 |
| Sonnet 5 | $0.00015 | $0.00337 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
goal 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 6d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 6d ago Changed 60df028cdeef
- 11d ago First seen · 86 lines · 74 tokens per session scan A 2e9060cae202
goal is a command published in the GitHub repository hamza-ali-shahjahan/hamzaish (8 stars, last pushed 5d ago), licensed AGPL-3.0. It adds 74 tokens to every session and 1,685 once invoked, about $0.0004 per session on Opus 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 commands, from other repositories
start
The first command in an AI Garage product-research workflow, where you study existing products instead of inventing a market from scratch. It searches for competitors with signs of demand and creates a shortlist in the project's docs folder.
status
A progress-check command for a project pipeline. It reads docs/STATE.md and compares its checklist with the project’s documented output files.
channel
A guided command for choosing one marketing channel using the target audience, buying intent, available time, and budget.
payments
A payment setup for a web product using Polar, a service that handles checkout, taxes, and subscription management for sellers.
validate
A five-question validation command for judging whether a competitor's product idea is worth pursuing. It checks traffic, revenue evidence, the competitor's main paid feature, build difficulty, and a possible way to reach users.
analytics
A website analytics setup that uses Plausible, PostHog, or both to track visitors, registrations, and purchases. Plausible focuses on simple privacy-friendly traffic data, while PostHog also tracks product actions and user journeys.