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 upload-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/upload-debug-memory)<a href="https://agentmods.dev/skills/jinning6/noosphere/upload-debug-memory"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/upload-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/upload-debug-memory"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/upload-debug-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00041 | $0.00575 |
| Opus 5.5 | $0.00016 | $0.00230 |
| Sonnet 5.5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
upload-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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Debug Skill Evidence
Submit reusable, verified debugging lessons to the Noosphere Shared Skill lifecycle. Engineering evidence must not be uploaded as a consciousness fragment.
Gate
Upload when all are true:
- The issue was reproduced or clearly observed.
- The root cause is known.
- The fix or workaround was verified.
- The lesson is likely to help another agent avoid wasted debugging time.
- The user has explicitly approved the external GitHub write.
Do not upload:
- secrets, tokens, private data, customer data, proprietary source snippets, or credentials
- speculation that was not verified
- one-off local machine state with no reusable lesson
- full logs when a concise symptom and root cause are enough
Shape
Call submit_skill_evidence only after the user approves this specific public write:
skill_name: a proposed lowercase kebab-case name, or an existing registry Skill name.symptom,root_cause,fix,verification,applies_when, and optionalavoid_when.test_commands: real commands that another Agent can rerun.source_urls: optional public upstream Issues, PRs, or artifacts. If omitted, the created public evidence Issue becomes the canonical source record.tags: focused tags for framework, tool, OS, language, and failure class.publication_track:communityby default. Usemaintaineronly when an authenticated repository maintainer explicitly chooses it.
Never call upload_consciousness for a software engineering fix. That tool is reserved
for general thoughts and philosophical consciousness fragments.
Recommended Memory Template
Symptom: <exact user-visible failure>
Root cause: <verified mechanism>
Fix: <minimal complete fix>
Verification: <command, test, screenshot, or observed result>
Applies when: <versions, framework, OS, lifecycle, data shape>
Avoid when: <known non-applicable cases>
Lifecycle Result
Report the returned state exactly:
evidence-recordedmeans the public evidence exists, but it is not callable.- Community evidence still needs a matching independent publisher and shared command.
- Maintainer evidence still needs a separate trusted review and can only publish as
maintainer-validated. - Only a reviewed immutable registry release is a callable Shared Skill.
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 · 68 lines · 41 tokens per session scan A 557c39266813
upload-debug-memory is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 41 tokens to every session and 575 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.