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/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/commands/jinning6/noosphere/noosphere-upload)<a href="https://agentmods.dev/commands/jinning6/noosphere/noosphere-upload"><img src="https://agentmods.dev/badge/commands/jinning6/noosphere/noosphere-upload/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/commands/jinning6/noosphere/noosphere-upload"><img src="https://agentmods.dev/badge/commands/jinning6/noosphere/noosphere-upload.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.00009 | $0.00227 |
| Opus 5.5 | $0.00004 | $0.00091 |
| Sonnet 5.5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
noosphere-upload 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.
What it actually says
Distill the resolved issue into reusable Shared Skill evidence. Ask for explicit consent
to create the public GitHub record, then call submit_skill_evidence.
Use this input as the focus:
$ARGUMENTS
Only submit if the issue was observed, the root cause is known, the fix was verified, and the user authorizes this specific public write. Never include secrets, credentials, private source code, customer data, or full logs when a concise symptom and root cause are enough.
Include a lowercase kebab-case Skill name, symptom, root cause, fix, verification, applicability boundaries, real test commands, optional external public source URLs, and focused tags. Use the community publication track unless an authenticated repository maintainer explicitly chooses the maintainer track.
Report the returned evidence URL and lifecycle state exactly. Do not describe an
evidence record as a published or callable Skill. Never route engineering evidence
through upload_consciousness.
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 · 28 lines · 9 tokens per session scan A 83eb2fc6cb27
noosphere-upload is a command published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed today), licensed Apache-2.0. It adds 9 tokens to every session and 227 once invoked, about $0.0000 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 commands, from other repositories
agent-brain-graph
Search using GraphRAG for relationship and dependency queries.
diagnose
Run a self-check on your AI Brain Starter install (CLAUDE.md, Meta folder, skills, hooks, MCPs).
provenance
Mostra a cadeia completa de proveniência de um finding - source, commit SHA, age, confidence atual com decay, lifecycle status. Útil para auditar de onde veio uma afirmação na camada compilada.
risk
Mostra riscos conhecidos para um path - código frágil, sem testes, magic, debt. Use antes de mexer em arquivos críticos.
slm-graph
Index any repo as a code knowledge graph and answer structural questions about it: callers, callees, impact radius, semantic search, and review context. These tools are not in the default tool set: they need slm tools set code (or whole); see "Tool set requirement" below.
matcha:audit
🍵 Stack health check — find overlaps, waste, and risks before they become problems.