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/klemensgc/modular-context-obsidian-plugin/module-scannergit clone --depth 1 https://github.com/klemensgc/modular-context-obsidian-pluginWhat 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.00038 | $0.00821 |
| Opus 5 | $0.00019 | $0.00411 |
| Sonnet 5 | $0.00008 | $0.00164 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
module-scanner 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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 87 lines · 38 tokens per session scan A 3f0eafb50f7b
module-scanner is an agent published in the GitHub repository klemensgc/modular-context-obsidian-plugin (97 stars, last pushed 26d ago), with no licence file. It adds 38 tokens to every session and 821 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
Sub Agents
Specialized sub-agents for spawnsubagent. Each agent is defined by a level-2 heading and a name: agent YAML fence directly below it.
knowledge-guide
Proactive methodology guidance agent. Monitors note creation and provides real-time quality advice. Suggests connections, flags quality issues, recommends MOC updates. Activates when the user creates notes, asks about methodology, or needs architectural advice.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
tdd-impl-agent
TDD (Test-Driven Development) implementation specialist. MUST BE USED when PM Auto-Dev requests TDD implementation for an issue. Reads context from tdd-context.json and outputs tdd-result.json. Follows Red-Green-Refactor cycle strictly.
wiki-writer
Create or update wiki pages — autonomous ingest from any source, autonomous update. Auto-creates .wiki/ if missing.
worker
Build worker on the routed model - writes code, edits files, executes specs. Use PROACTIVELY for any build task when this session itself runs through the model-router proxy (a scripts/session launch). In a normal direct-login session, do NOT use this agent - use the /fabsol flow's headless delegation instead, because…