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 nicholasglazer/gnosis-mcp --skill setupgit clone --depth 1 https://github.com/nicholasglazer/gnosis-mcpWrote 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/nicholasglazer/gnosis-mcp/setup)<a href="https://agentmods.dev/skills/nicholasglazer/gnosis-mcp/setup"><img src="https://agentmods.dev/badge/skills/nicholasglazer/gnosis-mcp/setup/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/nicholasglazer/gnosis-mcp/setup"><img src="https://agentmods.dev/badge/skills/nicholasglazer/gnosis-mcp/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 135 Skill accesses MCP server configuration files (mcp.json). MCP configs contain server URLs, authentication tokens, and tool definitions — reading them allows the skill to discover and potentially abuse other tool integrations.Fix: Remove all code or instructions that read MCP configuration files (mcp.json). MCP server details should be managed by the agent runtime, not read by individual skills.
- medium Rogue Agent · line 68 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- low MCP Rug Pull · line 27 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
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.00030 | $0.01649 |
| Opus 5.5 | $0.00012 | $0.00660 |
| Sonnet 5.5 | $0.00006 | $0.00330 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Then: `curl http://127.0.0.1:8000/api/search?q=auth&limit=5`. How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Gets you from nothing to "agent searching my docs" in 60 seconds.
Usage
/gnosis:setup # Interactive — asks where your docs live
/gnosis:setup /path/to/docs # Same, but ingest that folder right away
/gnosis:setup --postgres # Print PostgreSQL setup instructions too
Target: $ARGUMENTS
The procedure lives in one place
llms-install.md is the install procedure. Follow its agent checklist in order instead of re-deriving the steps here:
- Install the package —
pip install 'gnosis-mcp[embeddings,web]', oruv tool installwhen the machine has no suitable Python. gnosis-mcp init-db— creates the schema; idempotent.gnosis-mcp check— must printFTS5: readyand exit 0. If FTS5 is missing, stop and tell the user rather than ingesting: keyword search cannot work on that Python build.gnosis-mcp ingest <path> --dry-runto preview, thengnosis-mcp ingest <path> --embed.gnosis-mcp search "<a query you know the answer to>"— the first real verification.
Backend choice (SQLite by default; PostgreSQL for concurrent writers or > 100 k chunks), extras,
flags, write mode, and the platform notes (Windows .exe paths, WSL2, remote HTTP transport) are in
that file. If this skill and llms-install.md ever disagree, llms-install.md wins.
Claude Code extras — plugin, agents, skills
Search works with the MCP server alone; the extras are 5 subagents, 8 slash commands and a session-start hook. Two ways in:
- Plugin (Path A) —
claude plugin marketplace add nicholasglazer/gnosis-mcp, thenclaude plugin install gnosis, then restart Claude Code. - Manual copy (Path B) — clone the repo and copy the agents and skills you want into
.claude/agents/and.claude/skills/in your project. Exact commands, and how to cherry-pick a subset, are in Path B.
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 Changed · -85 lines 77a9285934aa
- 1mo ago First seen · 277 lines · 30 tokens per session scan A ab3ffa43d28f
setup is a skill published in the GitHub repository nicholasglazer/gnosis-mcp (29 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 1,649 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
accreta-setup
Set up an accreta knowledge base over a corpus — pick a preset, write the config and a source declaration, generate the constitution, wire up MCP, and verify the first ingest. Use when someone wants an agent-maintained knowledge base with provenance and drift detection over a codebase, a document collection, or a…
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.
memobase
A Russian-language skill for searching a local knowledge base built from documents and other sources such as web pages, YouTube, audio, and Obsidian notes.
kb-memory
Local-first agent memory and knowledge service (RAG) installed from PyPI. Use when a task needs to store or recall long-term user preferences, project decisions, facts, documents or web pages, when different projects need separate memories, or when the user mentions "kb memory", "kb", or a local MCP memory service.…
self_evolve_rag
This document describes how to use the Leeroopedia MCP tools for the Self-Evolving RAG task. It is kept as a reference and is NOT included in the agent prompt.