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 commands/geckse/markdown-vdb/build-appgit clone --depth 1 https://github.com/geckse/markdown-vdbWhat 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.00198 |
| Opus 5 | $0.00000 | $0.00099 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
build-app 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 2d 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
Build the Electron desktop app locally without publishing.
Steps:
- Ask the user which platform to build for: macOS, Windows, Linux, or all
cdto theapp/directory- Run
npm ciifnode_modules/looks stale or missing - Run the appropriate build command:
- macOS:
npm run build:mac - Windows:
npm run build:win - Linux:
npm run build:linux - All:
npm run build:all
- macOS:
- Report the output artifacts in
app/dist/
Notes:
- This does NOT push or publish anything — output stays in
app/dist/ - Cross-platform builds may not work (e.g., building Windows on macOS requires Wine)
- macOS code signing requires
CSC_LINKandCSC_KEY_PASSWORDenvironment variables for a signed build; without them, the build will be unsigned
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.
- 2d ago First seen · 18 lines · 0 tokens per session scan A bbfd28b9761c
build-app is a command published in the GitHub repository geckse/markdown-vdb (23 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 198 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
fieldtheory
Explain and drive the Field Theory CLI — bookmark-sourced seeds, repo-aware possibility runs that score ideas onto a 2x2 grid, and the interconnected .md files they leave behind. Trigger when the user asks about ft, bookmarks, seeds, ft possible (or the older name ft ideas), grids, dots/nodes, or how to turn saved…
wiki-init
Initialize a new LLM Wiki in the current directory. Creates the full directory structure, config, and template files.
check-invariants
Runs only the tree CRDT invariant test battery in outl-core. Faster than /check, focused on what can break sync.
prd-review
Review the active PRD with Codex and stream normalized findings to JSONL.
issue-amend
Re-snapshot the active issue's scope from the spec, clear verified and reviewed receipts, and record the change as a permanent amendment.
q-research
Read the research-mode skill's SKILL.md for the full ruleset before proceeding. Follow all constraints, the source lookup cascade, the token budget, and the "what counts as cited" rules exactly.