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/2233admin/obsidian-llm-wiki/issue-trackergit clone --depth 1 https://github.com/2233admin/obsidian-llm-wikiWhat 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.00000 | $0.00197 |
| Opus 5 | $0.00000 | $0.00098 |
| Sonnet 5 | $0.00000 | $0.00039 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
issue-tracker 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
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 26 lines · 0 tokens per session scan A 1cc2f2d90269
issue-tracker is an agent published in the GitHub repository 2233admin/obsidian-llm-wiki (29 stars, last pushed 9d ago), licensed GPL-3.0. It costs nothing until one of its globs matches a file; then it loads 197 tokens. 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
curator
Sub-agent dispatched by /mb:lint. Read-only — has Read + lint MCP tools but no Edit/Write/Bash. Surfaces orphans, contradictions, stale claims, gaps. Suggests fixes; doesn't apply them.
migrator
One-time sub-agent that runs /mb:migrate. Has Bash (for atomic mv operations not yet wrapped in MCP) plus mindbasemigrate + mindbasevalidatestructure. Should be invoked exactly once per legacy project.
builder
Sub-agent dispatched by /mb:build to synthesize context.md from sources/. Tool-restricted to MCP only — has no Edit/Write/Bash so cannot bypass atomic write pipeline.
contributor
Sub-agent dispatched for substantive contributions (PDFs, URLs, long pastes). Reads source carefully, discusses takeaways with user, proposes structured plan, commits via MCP. Cannot bypass append-only contract.
researcher
Sub-agent dispatched by /mb:research. Has WebFetch + WebSearch + Read + MCP researchsave + searchwiki tools. Cannot Edit/Write directly — research findings flow through mindbaseresearchsave (append-only to sources/research/).
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.