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 yeaight7/agent-powerups --skill memory-query-workflowgit 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/skills/yeaight7/agent-powerups/memory-query-workflow)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/memory-query-workflow"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/memory-query-workflow/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/yeaight7/agent-powerups/memory-query-workflow"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/memory-query-workflow.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.00522 |
| Opus 5.5 | $0.00013 | $0.00209 |
| Sonnet 5.5 | $0.00007 | $0.00104 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
memory-query-workflow 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Query Workflow
Overview
Use existing graph memory first.
Query the graph before rereading source files unless the graph is missing, stale, or too weak for the question.
Required Check
apx check graphify
Required State
- existing
graphify-out/graph.json
Routing
| Question shape | Action |
|---|---|
| broad question about connected concepts | graphify query |
| trace between two concepts, files, or systems | graphify path |
| explain one concept or node in context | graphify explain |
| no graph exists | switch to memory-build-workflow |
| graph exists but corpus changed | recommend graphify --update before trusting results |
Core Rules
- prefer graph retrieval over full-corpus reread
- say explicitly when the graph is missing, stale, sparse, or weakly matched
- do not overclaim beyond what graph nodes and edges support
- when graph coverage is weak, use the graph result to target the next direct read instead of restarting broad exploration
Minimal Workflow
- Confirm
graphify-out/graph.jsonexists. - Choose
query,path, orexplainbased on question shape. - Answer from graph evidence first.
- If result quality is weak, say why: missing graph, stale graph, low coverage, or weak node match.
- Escalate to build/update or targeted reread only when needed.
Common Failure Modes
- skipping graph lookup and rereading everything
- hiding that the graph is stale or incomplete
- using
queryfor a question that clearly needs a path trace - treating no-result output as proof the corpus lacks the concept
Verification
- Graph existence was confirmed before any query ran
- The command matched the question shape: query for breadth, path for traces, explain for one node
- The answer is grounded in graph nodes and edges — no overclaiming
- Staleness, sparseness, or weak node matches were stated explicitly
- Escalation to build, update, or targeted reread happened only when graph evidence was insufficient
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 · 67 lines · 33 tokens per session scan A 5f1b98619921
memory-query-workflow is a skill published in the GitHub repository yeaight7/agent-powerups (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 522 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-09-14.
Other skills, from other repositories
persistent-notes
Save notes locally to /mnt/workspace/notes.json file. Use when user wants to "save a note" or "remember something".
session-summaries
What the chat right-panel session summary shows, what it costs, and how to make a session summarize well. Load when the user asks about the session summary panel, why a summary looks wrong or empty, or how to turn it on.
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.
bmad-deep-recon
Research a topic to support a decision, three ways: draft a research prompt for the user to run in their own tool (ChatGPT, Gemini, Grok, Perplexity, …), turn a finished research report into a short summary with cited sources that other skills can use directly, or run the research here with parallel web searches.…
bmad-ticket
Create and manage tickets — initiatives, epics, stories, bugs. Use when the user says "create a new initiative", "slice this initiative", "split this epic up", "break this into stories", "incept this epic", "make a ticket", "refine this ticket", "what's ready", "status of a story", "publish ticket changes", "validate…
bmad-eval
Runs the evals of a BMad skill through the agent harness the user works in and reports what they show: baseline against the bare model, variant against a stripped or prior version, quality against a rubric, and trigger accuracy of the description with an optional optimization loop. Use when the user asks to evaluate…