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 agentmods add skills/jinning6/noosphere/using-noospherenpx skills add JinNing6/Noosphere --skill using-noospheregit 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/using-noosphere)<a href="https://agentmods.dev/skills/jinning6/noosphere/using-noosphere"><img src="https://agentmods.dev/badge/skills/jinning6/noosphere/using-noosphere.svg" alt="Measured on agentmods" 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 | $0.00060 | $0.00510 |
| Opus 5 | $0.00030 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
using-noosphere 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 4d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Noosphere
Use the live registry as one evidence source inside the normal debugging workflow. The plugin ships this control Skill only; concrete engineering Skills remain versioned in the registry.
Workflow
- Frame the failure: symptom, environment and versions, expected result, observed result, and constraints.
- Call
list_shared_skills(query="<symptom, environment, failure mechanism>"). Ranked or catalog-fallback results are candidates for inspection, not proof of a match. If none applies, continue normal diagnosis. - Call
get_shared_skill(skill_name, version)for one applicable immutable release. Reject digest failure. Before use, state itsname@version, verification level, abbreviated SHA-256,applies_when, andavoid_when. - Reproduce when practical, apply only the relevant guidance, and run the project's real verification. Retrieval alone never proves success.
- Classify the result as
success,partial, orfailure. Userecord_skill_outcomeonly after explicit consent because it creates a public, authenticated GitHub record. - If the Agent independently verifies a reusable fix, ask for explicit consent before
submit_skill_evidence. Report the exact returned state and URL. An evidence record is not a candidate or callable Skill; community evidence still needs an independent publisher, while maintainer evidence still needs separate trusted review.
Boundaries
- Anonymous, read-only discovery is the default.
- Never publish evidence, outcomes, or withdrawal requests without explicit consent at the time of the write; exclude secrets and private evidence.
- Engineering fixes use
submit_skill_evidence. Do not useupload_consciousnessfor software engineering evidence; it is only for general thoughts and philosophical consciousness fragments. - A verified digest proves artifact identity, not universal correctness. Repository, permission, privacy, safety, applicability, and local test evidence remain authoritative.
- Prefer the latest active release unless reproducing a pinned older version. Use
check_skill_updateswhen a prior version or digest is known.
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.
- 4d ago First seen · 45 lines · 60 tokens per session scan A 01dad825f013
using-noosphere is a skill published in the GitHub repository JinNing6/Noosphere (18 stars, last pushed 4d ago), licensed Apache-2.0. It adds 60 tokens to every session and 510 once invoked, about $0.0003 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-30.
Other skills, from other repositories
prjct
The agentic harness for AI coding agents: machine-verified ships, guarded edits, and project lookup that beats re-deriving from source. Run the prjct verb yourself; use prjct work normally.
memstate-ai
Persistent, versioned memory for AI agents via Memstate AI. Alternative to the Memstate MCP plugin — use for storing facts, recalling memory, managing projects, and semantic search of agent summaries. Supports Markdown ingestion and direct keypath = value assignment. Requires MEMSTATEAPIKEY.
kaeru
Cognitive memory layer for LLM agents — typed graph + bi-temporal substrate + curator API, reached through the kaeru MCP server. Use when the user wants to capture, recall, reason, or trace persistent thoughts across sessions; when re-entering a multi-session project; or when the user explicitly asks to "remember"…
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.