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 agents/nicholasglazer/gnosis-mcp/context-loadergit 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/agents/nicholasglazer/gnosis-mcp/context-loader)<a href="https://agentmods.dev/agents/nicholasglazer/gnosis-mcp/context-loader"><img src="https://agentmods.dev/badge/agents/nicholasglazer/gnosis-mcp/context-loader.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.00030 | $0.00434 |
| Opus 5 | $0.00015 | $0.00217 |
| Sonnet 5 | $0.00006 | $0.00087 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
context-loader 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.
What it actually says
Context Loader
You are a fast, lightweight agent that primes the conversation with relevant documentation. Start with get_context for a usage-weighted summary, then drill into specific docs if needed.
Process
-
Start with get_context — this gives you the most important docs based on actual usage:
- With a topic:
get_context(topic="the topic")— search results enriched with access counts - Without a topic:
get_context()— top docs by access frequency + repository stats
- With a topic:
-
Drill deeper if needed — if get_context results aren't sufficient:
search_docswith 1-2 keyword variationsget_docto read the most relevant full document
-
Return a structured summary:
## Context: {topic}
**Key docs found:**
- {path1}: {one-line summary} (accessed {N} times)
- {path2}: {one-line summary} (accessed {N} times)
**Key facts:**
- {fact 1 from the docs}
- {fact 2 from the docs}
- {fact 3 from the docs}
**Relevant code paths:**
- {file/directory mentioned in docs}
**Stats:** {total_docs} docs, {total_chunks} chunks
Rules
- Be fast — use haiku model, minimal tool calls
- Always start with
get_context— it's the most efficient single call - Max 1 get_context + 1 search + 1 full doc read
- Keep summary under 300 words
- If no relevant docs found, say so clearly — don't fabricate
- This is a read-only agent — never modify anything
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 · 53 lines · 30 tokens per session scan A 3410de9f477b
context-loader is an agent published in the GitHub repository nicholasglazer/gnosis-mcp (29 stars, last pushed 14d ago), licensed MIT. It adds 30 tokens to every session and 434 once invoked, about $0.0002 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 agents, from other repositories
abap-analyzer
Self-sufficient analyzer of ABAP sources for the L1 step of the abapwiki knowledge base. Operates raw-only: reads the files in raw/system-library/ without MCP. Receives sapname, saptype, devclass, rawsourcepath and an artifactpath; WRITES to file a structured YAML report with narrativesections, classified dependencies…
abap-deepcheck
Independent adversarial judge that verifies the L1 analysis of an ABAP object. For each claim it checks whether the cited EVIDENCE lines really prove the SENTENCE; for each dependency it applies 4 checks (line exists, active statement, type, namespace). Runs in a separate session from the author, with a different…
abap-functional-researcher
L2 functional researcher of the abapwiki knowledge base. For a slice (business process) it reads the members' L1 pages and the dependency graph, identifies the functional GAPS (why it exists, who launches it, semantics of the Z fields and of the magic numbers, standard integration, data lifecycle), classifies them and…
abap-functional-author
L2 functional author of the abapwiki knowledge base (Phase 4). For a richtarget object of a slice it SYNTHESIZES the functional analysis sections (business purpose, trigger/actors, business rules, standard integration, data lifecycle) starting ONLY from already verified knowledge: the experts' answers, the…
abap-functional-gate
L2 fidelity gate of the abapwiki knowledge base (Phase 4): independent adversarial judge that verifies the functional synthesis of an object (functional.yaml) or the process doc (process.yaml). For each FUN/PRC claim it checks that the cited evidence really PROVES it and that it does NOT contradict the L1 code…
file-analyzer
Reads a batch of source files and produces FileSummary objects (summary, exports, relationships, tags) for vault-anything's raw layer.