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 Yakoub-ai/neural-memory --skill neural-inspectgit 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/skills/yakoub-ai/neural-memory/neural-inspect)<a href="https://agentmods.dev/skills/yakoub-ai/neural-memory/neural-inspect"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-inspect/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/yakoub-ai/neural-memory/neural-inspect"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-inspect.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.00034 | $0.00502 |
| Opus 5 | $0.00017 | $0.00251 |
| Sonnet 5 | $0.00007 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
neural-inspect 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 10d 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 — Deep Inspect
Deep-dive into a specific code element — see its full context in the knowledge graph.
What you get
- Full summary: Detailed explanation of purpose, logic, and interface
- Parent: Which module or class contains this
- Callers: Who calls this function (upstream)
- Callees: What this function calls (downstream)
- Siblings: Other functions/methods at the same level
- Children: Contained elements (methods in a class, etc.)
- Call chains: Trace execution paths up and down the graph
- Source code: The actual implementation (optional)
How to call
Via MCP tool (neural-memory configured as MCP server in Claude Code):
Tool: neural_inspect
{ "node_id": "module::ClassName.method_name" }
or by name:
{ "node_name": "method_name", "show_code": true, "trace_calls": true }
Via Python (working directly in the project):
import asyncio
from neural_memory.server import neural_inspect, InspectInput
# By node_id (most precise — get from neural_query results)
asyncio.run(neural_inspect(InspectInput(node_id="module::ClassName.method_name")))
# By name (fuzzy match)
asyncio.run(neural_inspect(InspectInput(node_name="method_name", show_code=True, trace_calls=True)))
Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
node_id |
str | None | Exact node ID from query results (most precise) |
node_name |
str | None | Name to fuzzy-search (use if you don't have the ID) |
project_root |
str | "." |
Project root directory |
show_code |
bool | false |
Include raw source code in output |
trace_calls |
bool | false |
Show full upstream/downstream call chains |
Provide either node_id or node_name — node_id is preferred when available.
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.
- 10d ago First seen · 54 lines · 34 tokens per session scan A 2c22c4184714
neural-inspect is a skill published in the GitHub repository Yakoub-ai/neural-memory (1 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 502 once invoked, about $0.0002 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 skills, from other repositories
calibration-diff
Compare the current Claude Code setup against the previous calibration run's baseline. Spawns only the evaluator (pass 2) — no planner, no calibrator, no edits. Useful between calibration runs (you manually edited a few files; what now shows resolved vs new?) and as a "did my changes hold up?" check after merging a…
calibration-doctor
Fast structural health check for a Claude Code setup. Detects broken config — JSON that doesn't parse, hook scripts that are missing or non-executable, subagent/skill files with malformed frontmatter, MCP servers whose command can't be found, and .gitignore that's missing .claude/calibration/. Prints a terse triage…
calibrate-settings
Audits and tunes every settings.json Claude Code reads — user (/.claude/settings.json), user-local (/.claude/settings.local.json), project (.claude/settings.json), project-local (.claude/settings.local.json), and plugin-self when the project is itself a plugin. Flags committed secrets, --dangerously-skip-permissions…
automation-debugger
Expert automation platform error debugger for Power Automate, n8n, Make, Zapier and other workflow platforms. Analyzes JSON flow definitions with error messages, researches official documentation, and generates complete fixed JSON ready for copy-paste. Triggers when user provides error JSON files, workflow JSON with…
automation-quick-fix
Fast automation platform error resolver for Power Automate, n8n, Make, Zapier and other platforms. Handles common patterns like 401/403 auth errors, 429 throttling, and data format issues. Provides immediate fixes without deep research for well-known error patterns. Use when error matches common scenarios (status…
automation-validator
Validates automation workflow JSON before deployment for Power Automate, n8n, Make, Zapier and other platforms. Checks syntax, structure, best practices, and potential issues. Analyzes workflow JSON files for platform compliance, missing error handling, performance issues, and security concerns. Use when user wants to…