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/Yakoub-ai/neural-memoryWrote 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/yakoub-ai/neural-memory/neural-query)<a href="https://agentmods.dev/commands/yakoub-ai/neural-memory/neural-query"><img src="https://agentmods.dev/badge/commands/yakoub-ai/neural-memory/neural-query.svg" alt="Measured on agentmods" 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.00286 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
neural-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 7d 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
Neural Memory — Query
Search the neural knowledge graph for functions, classes, modules, or concepts.
What this does
Returns layered results:
- Short summary: Understand what a node does at a glance
- Node ID: Use with
/neural-inspectto go deeper - Location: File path and line numbers
How to call
Via MCP tool (neural-memory configured as MCP server in Claude Code):
Tool: neural_query
{ "query": "your search term", "limit": 10 }
Via Python (working directly in the project):
import asyncio
from neural_memory.server import neural_query, QueryInput
asyncio.run(neural_query(QueryInput(query="your search term")))
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
query |
str | required | Function name, class name, or concept keyword |
project_root |
str | "." |
Project root directory |
limit |
int | 10 |
Max results (1–50) |
Results are ranked by importance score — the most connected, public-facing code appears first.
Use /neural-inspect on any result's node_id to see full context, callers, callees, and source code.
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.
- 7d ago First seen · 37 lines · 0 tokens per session scan A 7bdf11ae710f
neural-query is a command published in the GitHub repository Yakoub-ai/neural-memory (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 286 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 commands, from other repositories
audit-release
Diagnose release-readiness against the Starter Series quality bar — matched starter, version-vs-last-tag drift, CHANGELOG drift vs merged PRs, and publish-workflow kind. Read-only.
repo-orch-deliberate
Adversarial multi-repo root-cause mode: spawn all repo specialists as an Agent Team, force them to challenge each other's assumptions with evidence, and surface the true cross-repo root cause of an incident. Max 3 deliberation rounds with a tie-break rule.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
debug
Systematic debugging with hypotheses and evidence gathering.
data-flow-analysis
Trace how data flows through the system from input to output.
duck-off
Turn off Rubber Duck mode and answer normally.