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-add-buggit 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-add-bug)<a href="https://agentmods.dev/skills/yakoub-ai/neural-memory/neural-add-bug"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-add-bug/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-add-bug"><img src="https://agentmods.dev/badge/skills/yakoub-ai/neural-memory/neural-add-bug.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.00036 | $0.00513 |
| Opus 5 | $0.00018 | $0.00257 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
neural-add-bug 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 11d 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 — Add Bug
Manually create a bug node in the knowledge graph. Use this when you discover a bug during a session and want it indexed immediately, without waiting for a context log re-import.
How to call
Via MCP tool (neural-memory configured as MCP server in Claude Code):
Tool: neural_add_bug
{
"description": "What went wrong",
"severity": "high",
"file_path": "neural_memory/parser.py",
"line_start": 142,
"root_cause": "Off-by-one in slice index",
"fix_description": "Changed range(n) to range(n+1)"
}
Via Python (working directly in the project):
import asyncio
from neural_memory.server import neural_add_bug, AddBugInput
asyncio.run(neural_add_bug(AddBugInput(
description="What went wrong",
severity="high",
file_path="neural_memory/parser.py",
line_start=142,
root_cause="Off-by-one in slice index",
fix_description="Changed range(n) to range(n+1)",
)))
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
description |
Yes | str | What went wrong (min 3 chars) |
severity |
No | str | "low" / "medium" / "high" / "critical" (default: "medium") |
file_path |
No | str | Source file this bug relates to |
line_start |
No | int | Starting line number |
line_end |
No | int | Ending line number |
root_cause |
No | str | Root cause description |
fix_description |
No | str | How it was or should be fixed |
project_root |
No | str | Project root (default: ".") |
Notes
- The bug node is linked to matching code nodes via
RELATES_TOedges - It will appear in
/neural-queryresults alongside code nodes - Bugs are also auto-imported from
.claude/context-log-gotchas.mdon every/neural-index
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.
- 11d ago First seen · 57 lines · 36 tokens per session scan A 4c8bc2659346
neural-add-bug is a skill published in the GitHub repository Yakoub-ai/neural-memory (1 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 513 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
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
error-recovery
Maintains a project-specific known-issues.md mapping recurring errors to their solutions. Consulted automatically by systematic-debugging before investigation. Saves time by avoiding rediscovery of known problems across sessions. Triggers on: "save this fix", "remember this error", "known issues", or automatically…
esp32-expert
This skill should be used for ESP32-specific hardware and runtime work in ESP-IDF, Arduino-ESP32, or PlatformIO projects: target/build detection, FreeRTOS tasks and ISRs, memory/DMA, peripherals, power, networking/security, OTA, crash diagnosis, and unattended reliability. Trigger on "debug this ESP32 crash", "review…
Closure Scope Retention Guard
Detects long-lived objects (caches, listeners, singletons) that capture an entire enclosing scope via closures/environment capture, keeping large arrays or buffers alive, and proposes copying only the needed fields.
capturing-learnings
Records a real failure-and-fix pair as a project-local lesson, with the specifics that make it recognisable next time. Use when a bug, leakage mistake, or validation error was found and corrected and should not recur. Use when someone asks to save what was learned from an experiment that went wrong.
vibe-debugging-journal
Records resolved bugs in a persistent journal — symptom, root cause, difficulty, fix, prevention. Organized by category for future reference.