sage-wiki-integrate

sage-wiki-integrate is a skill for Claude Code, Codex from xoai/sage-wiki. It costs 33 tokens per session (873 once invoked), scanned A, original, MIT.

A setup pipeline that connects sage-wiki, a knowledge service that stores information with its source history, to an existing code project. It detects whether the project uses Python or JavaScript/TypeScript, installs the matching client, and checks the connection.

In plain words
What is it for?
Use it to add sage-wiki to a Python, JavaScript, or TypeScript repository, configure its client or MCP connection, and run a smoke test.
Why use it?
It removes the guesswork from choosing an integration method and checking whether the setup works. Projects without those language markers can use MCP, a standard way for agents to connect to external tools and data.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to add sage-wiki to a Python, JavaScript, or TypeScript repository, configure its client or MCP connection, and run a smoke test.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xoai/sage-wiki/sage-wiki-integrate
Install

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.

Any agent
npx skills add xoai/sage-wiki --skill sage-wiki-integrate
Clone the repo
git clone --depth 1 https://github.com/xoai/sage-wiki

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for sage-wiki-integrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/xoai/sage-wiki/sage-wiki-integrate/github.svg)](https://agentmods.dev/skills/xoai/sage-wiki/sage-wiki-integrate)
Your own site
<a href="https://agentmods.dev/skills/xoai/sage-wiki/sage-wiki-integrate"><img src="https://agentmods.dev/badge/skills/xoai/sage-wiki/sage-wiki-integrate/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.

agentmods 80×15 button for sage-wiki-integrate

Your own site · 80×15
<a href="https://agentmods.dev/skills/xoai/sage-wiki/sage-wiki-integrate"><img src="https://agentmods.dev/badge/skills/xoai/sage-wiki/sage-wiki-integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 873 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00873
Opus 5.5 $0.00013 $0.00349
Sonnet 5.5 $0.00007 $0.00175
Haiku 4.5 $0.00003 $0.00087

Measured 1mo ago against content hash ef23086b4117, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sage-wiki-integrate 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.

skills/sage-wiki-integrate/SKILL.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sage-wiki-integrate

Wires sage-wiki into an existing repository so the coding assistant can store and retrieve knowledge with provenance. Test-first — every step is verified before proceeding.

Step 1: Detect language

Check the project root for language markers:

Marker Language Integration path
pyproject.toml Python pip install sagewiki (Python client, P4-3)
package.json TypeScript / JavaScript npm install sagewiki (TypeScript client, P4-4)
Neither Any MCP stdio config

Step 2: Choose integration path

Python (pyproject.toml found)

pip install sagewiki
from sagewiki import Client

client = Client(base_url="http://localhost:3333/v1")
# If token-protected:
# client = Client(base_url="http://localhost:3333/v1", token="s3cret")

TypeScript (package.json found)

npm install sagewiki
import { Client } from "sagewiki";

const client = new Client({ baseUrl: "http://localhost:3333/v1" });
// If token-protected:
// const client = new Client({ baseUrl: "http://localhost:3333/v1", token: "s3cret" });

Neither (MCP stdio)

Add to the project's MCP config:

{
  "mcpServers": {
    "sage-wiki": {
      "command": "sage-wiki",
      "args": ["serve", "--transport", "stdio", "--project", "."]
    }
  }
}

Step 3: Write a smoke test

Store a fact, search for it, verify it comes back:

Python smoke test:

# Store a fact via capture
resp = client.capture(content="smoke-test: sage-wiki integration works at {now}")
assert resp.status == "ok"

# Search for it
results = client.search(query="smoke-test sage-wiki integration")
assert len(results) > 0, "smoke test failed: no results for stored fact"
print("PASS: smoke test")

TypeScript smoke test:

const resp = await client.capture({ content: "smoke-test: sage-wiki integration works" });
const results = await client.search({ query: "smoke-test sage-wiki integration" });
console.assert(results.length > 0, "smoke test failed");
console.log("PASS: smoke test");

Read the full file on GitHub · 123 lines

Changes

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.

  1. 1mo ago First seen · 123 lines · 33 tokens per session scan A ef23086b4117

Subscribe to this mod's changes

sage-wiki-integrate is a skill published in the GitHub repository xoai/sage-wiki (638 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 873 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

knowledge-ingest

Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn). Routes meetings to knowledge-meeting-ingest and short thoughts…

openclaw/openclaw · 67 tokens

mem0-oss-to-platform

Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…

mem0ai/mem0 · 217 tokens

forget

Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…

asgeirtj/system_prompts_leaks · 74 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

memory

Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.

opensquilla/opensquilla · 44 tokens

ha-data-stores

Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…

shiwenwen/hope-agent · 115 tokens