Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ussumant/llm-wiki-compiler/plugin install llm-wiki-compilerWrote 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/commands/ussumant/llm-wiki-compiler/fetch-bookmarks)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/fetch-bookmarks"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/fetch-bookmarks.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.1 | $0.00000 | $0.01339 |
| Opus 5 | $0.00000 | $0.00669 |
| Sonnet 5 | $0.00000 | $0.00268 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
fetch-bookmarks 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Bookmarks from an External Source
Pull bookmarks from an external service (X/Twitter today; Readwise, Pocket, GitHub stars planned) into a local directory that /wiki-compile can consume. Optional — only needed when you want wiki topics synthesized from external sources, not just files already on disk.
The command itself is a thin dispatcher. Each source has its own adapter file that handles dependency checks, auth, sync, and wiring.
Instructions
Step 1: Parse arguments
Accept one of these forms:
/fetch-bookmarks <source>— sync once (default)./fetch-bookmarks schedule <source>— install a daily auto-sync job./fetch-bookmarks schedule <source> --uninstall— remove the auto-sync job./fetch-bookmarks(no args) — list available adapters and usage; then stop.
When listing adapters, glob ${CLAUDE_PLUGIN_ROOT}/skills/wiki-compiler/adapters/*.md:
Usage:
/fetch-bookmarks <source> Sync once
/fetch-bookmarks schedule <source> Install daily auto-sync
/fetch-bookmarks schedule <source> --uninstall Remove auto-sync
Available sources:
- x — X/Twitter bookmarks (via Field Theory CLI)
More adapters planned: readwise, pocket, github-stars.
Step 2: Locate the adapter
- Resolve the adapter file at
${CLAUDE_PLUGIN_ROOT}/skills/wiki-compiler/adapters/{source}.md. - If the file does not exist, print:
Then stop.No adapter for "{source}" yet. Available: {list}. Want to contribute one? See adapters/x.md for the contract.
Step 3a: One-off sync (default)
- Read the adapter file in full.
- Follow its numbered steps in order. Each adapter is self-contained and handles its own preflight, consent prompts, sync, and config updates.
- Surface the adapter's step-by-step progress to the user as you go. Do not retry failing steps silently — if a step fails, stop and show the error.
- After successful completion, print:
Do not auto-invokeBookmarks fetched. Run /wiki-compile to synthesize them into topic articles./wiki-compile.
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.
- 7d ago First seen · 101 lines · 0 tokens per session scan A 4d581978a64d
fetch-bookmarks is a command published in the GitHub repository ussumant/llm-wiki-compiler (321 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,339 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.