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 JinNing6/Noosphere --skill agent-debug-memorygit clone --depth 1 https://github.com/JinNing6/NoosphereWrote 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/jinning6/noosphere/agent-debug-memory)<a href="https://agentmods.dev/skills/jinning6/noosphere/agent-debug-memory"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/agent-debug-memory/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/jinning6/noosphere/agent-debug-memory"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/agent-debug-memory.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.00050 | $0.00510 |
| Opus 5.5 | $0.00020 | $0.00204 |
| Sonnet 5.5 | $0.00010 | $0.00102 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
agent-debug-memory 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Debug Memory
Use Noosphere as the shared debugging memory layer before and after substantial debugging work.
Before Fixing
- Extract a precise query from the failure:
- exact error text, stack frame, failing command, failing test, or visible symptom
- framework, package, runtime, OS, database, browser, or deployment context
- the user's concrete goal and any constraints already stated
- Call the Noosphere MCP tool
consult_noospherewith that query. - If useful tags are obvious, include focused
topic_tags, such asreact,vite,typescript,mcp,github-actions,async-ui,codex,claude-code,windows, or the library name. - Treat returned fragments as leads, not truth. Verify against the local codebase, official docs when needed, and runnable tests or reproduction steps.
During Fixing
- Prefer the smallest complete fix that addresses the verified root cause.
- Do not copy a Noosphere fragment blindly if the local environment, version, lifecycle, or data flow differs.
- Keep secrets, tokens, private customer data, private code snippets, and credentials out of tool calls and uploaded memories.
After Fixing
When the outcome is verified, the lesson is reusable, and the user explicitly approves the external GitHub write, upload a distilled memory with upload_consciousness.
Use:
consciousness_type: "warning"for pitfalls, footguns, version traps, and failure modes.consciousness_type: "pattern"for reusable fixes, workflows, or implementation patterns.consciousness_type: "decision"for tradeoff-heavy engineering choices.
The uploaded memory should include:
- the symptom or failing command
- the root cause
- the fix
- the verification command or evidence
- version or environment details that prevent false reuse
Keep the memory concise and general enough for another agent to reuse.
Completion Standard
Do not claim the fix is complete until local verification has passed or you have clearly stated what could not be run. Public registry reads work anonymously; uploading evidence or outcomes requires a GitHub token in the Agent's Noosphere MCP environment.
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 · 49 lines · 50 tokens per session scan A d15ebefd3fa2
agent-debug-memory is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 50 tokens to every session and 510 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
honcho-cli
Inspect and debug Honcho workspaces via the honcho CLI. Use when investigating peer representations, memory state, session context, or dialectic quality — any task that requires introspection of a Honcho deployment, including verifying that a recall/record memory loop is actually working.
brain-doctor
Lint and repair the Claude Brain Logseq graph — find and fix format violations that create phantom pages or broken macros. Triggers: "brain doctor", "lint brain", "check brain health", "clean up brain", "fix brain", "graph hygiene", "why are there empty pages", "find broken pages", "backfill digests", "rebuild digest…
diagnose
Use when an AI Brain vault needs a health check or something feels off: Claude ignores CLAUDE.md, journal entries missing from /weekly, hooks not firing, something broke after a git pull, a friend's install misbehaves, Obsidian crashes or pegs the CPU, a .claude/worktrees folder appeared, Granola/WhatsApp/Slack/Gmail…
troubleshooting
Diagnoses and repairs core-memory-kit itself when the memory system is broken — the per-failure-code repair book. Fire whenever a "⚠ [core-memory-kit]" whisper appears on the prompt (it names the failure and points here), or when the user reports a kit symptom however they phrase it: memory is not being saved, nothing…
status
Check Nowledge Mem connection status, server version, CLI version, and configuration. Use when diagnosing issues or verifying setup.
source-command-hooks-post-edit
Migrated source command hooks-post-edit.