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/brain-ask)<a href="https://agentmods.dev/commands/hamza-ali-shahjahan/hamzaish/brain-ask"><img src="https://agentmods.dev/badge/commands/hamza-ali-shahjahan/hamzaish/brain-ask/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/brain-ask"><img src="https://agentmods.dev/badge/commands/hamza-ali-shahjahan/hamzaish/brain-ask.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.00489 |
| Opus 5.5 | $0.00000 | $0.00196 |
| Sonnet 5.5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
brain-ask 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.
What it actually says
The user invoked: /brain-ask $ARGUMENTS — or you reached for recall yourself (a cross-cutting question, a past decision, the start of a fresh session on an unfamiliar product).
- If the query is empty, ask the user what they want to find.
- Query (via
Bash) — it refreshes the index itself before answering, so there is no reindex step to remember:
Abun ${HAMZAISH_ROOT:-$HOME/Claude/Hamzaish}/brain/ask.ts $ARGUMENTS⟳ index was behind the files — refreshednote on stderr is normal and means it caught up before answering. Scoping when results are noisy:--product <slug>,--source brain/learnings,--limit 4 --json. Phrase-quote for exact wording ("Sean Ellis target"); multi-word terms are OR'd and BM25-ranked. - Show the markdown output as-is — it's already formatted with citations (path + source tag + score + snippet).
Readthe top 2–3 hits before answering, and cite the source file paths so the user can verify.- If results are empty, they are empty against a just-refreshed index — treat it as genuinely uncharted and retry with broader terms, not as a missed reindex.
What you don't do
- Don't run
brain/ingest.tsfirst "to be safe" — ask refreshes itself, and the extra run is pure latency. Run it directly only to rebuild on demand. - Don't paraphrase from snippets alone — snippets are 18 tokens of context, not the full picture.
Readthe hits. - Don't substitute brain-ask for reading a file the user named directly. brain-ask is for discovery, not retrieval-by-path.
Sources: brain/README.md (what's indexed, how it works), brain/schema.sql (the database shape).
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 · 25 lines · 0 tokens per session scan A d1a7acece360
brain-ask is a command published in the GitHub repository hamza-ali-shahjahan/hamzaish (10 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 489 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.
brain-ask compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| brain-askhamza-ali-shahjahan/hamzaish | Command | 10 | 1mo ago | MIT | A | 0 | Claude Code |
| minutes-ideassilverstein/minutes | Command | 1.6k | yesterday | MIT | A | 48 | Claude Code, OpenCode |
| learnReflexioAI/claude-smart | Command | 791 | 3d ago | Apache-2.0 | A | 14 | Claude Code |
| memory-storeverygoodplugins/mcp-automem | Command | 66 | yesterday | MIT | A | 10 | Claude Code |
| cc-memoryTheLobbi/claude | Command | 21 | 7d ago | MIT | A | 0 | Claude Code |
| lians-recallLians-ai/Lians | Command | 17 | 5d ago | Apache-2.0 | A | 19 | Claude Code |
| recallnaimkatiman/continuous-improvement | Command | 9 | 5d ago | MIT | A | 44 | Claude Code |