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/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/memory-query)<a href="https://agentmods.dev/commands/yeaight7/agent-powerups/memory-query"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/memory-query/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/yeaight7/agent-powerups/memory-query"><img src="https://agentmods.dev/badge/commands/yeaight7/agent-powerups/memory-query.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.00025 | $0.00511 |
| Opus 5 | $0.00013 | $0.00255 |
| Sonnet 5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
memory-query 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 yesterday.
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
Objective
Use graph-backed memory first. Query existing graph state before reopening source documents.
Context
Input: a user question, node name, or relationship target from $ARGUMENTS.
Expected state:
graphify-out/graph.jsonalready exists for the target corpusgraphifyis available for query, path, or explain flows
Process
- Check
apx check graphify. - Confirm
graphify-out/graph.jsonexists before answering from graph memory. - If
graphifyis missing, stop and report the missing requirement. If the graph file is missing, stop and route tomemory-build. - Route the request to one primary flow:
- broad question, topic lookup, or "what do we know about X?" ->
graphify query - relationship trace, dependency chain, or "how does X connect to Y?" ->
graphify path - concept/node explanation or "explain X" ->
graphify explain
- broad question, topic lookup, or "what do we know about X?" ->
- Check freshness before leaning on the answer:
- if the corpus changed after the graph was built, say the graph may be stale
- recommend
memory-buildorgraphify --updatebefore treating the answer as current
- If the graph answer is weak, partial, or clearly off-route, say so explicitly and recommend either refresh or targeted source reread.
Stop Conditions
graphifyrequirement check failsgraphify-out/graph.jsondoes not exist- user is asking for current corpus state but the graph is known stale enough that the answer would mislead
- query intent is ambiguous enough that query/path/explain routing would likely choose the wrong flow
Rules
- prefer graph retrieval over corpus reread
- do not hallucinate edges, nodes, or freshness
- do not silently fall back to full-corpus reread unless the user asked for it or graph retrieval is unusable
- if graph answer is weak, say so and recommend refresh or targeted source read
graphify queryis default only for broad retrieval; usepathandexplainwhen the question shape is narrower
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.
- yesterday First seen · 52 lines · 25 tokens per session scan A 5b77de75a23c
memory-query is a command published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 25 tokens to every session and 511 once invoked, about $0.0001 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-09-14.
Other commands, from other repositories
compound
Document a solved problem to compound team knowledge.
sessions
Manage Claude Code session history, aliases, and session metadata.
save-session
Save current session state to a dated file in /.claude/session-data/ so work can be resumed in a future session with full context.
instinct-import
Import instincts from file or URL into project/global scope.
instinct-status
Show learned instincts (project + global) with confidence.
instinct-export
Export instincts from project/global scope to a file.