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/windviki/vbookmarks/releasegit clone --depth 1 https://github.com/windviki/vBookmarksWhat 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.02072 |
| Opus 5 | $0.00000 | $0.01036 |
| Sonnet 5 | $0.00000 | $0.00414 |
| Haiku 4.5 | $0.00000 | $0.00207 |
Grade A, and why
release 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release: Build, Package & Publish (detail)
Extracted verbatim from
AGENTS.md— the detailed halves of "Build (release)", "Packaging (deployment)" and "Release process".AGENTS.mdkeeps the command summary and the step outline.
Build & Packaging
Since 4.1.0 the release form is dist/ (esbuild bundle + Terser minify, same-path structure — the dev flow stays build-free):
npm run build # dist/ + build-time self-checks (fails on contract breaks; see docs/plan-4.1.0/build-and-performance-plan.md §3.1)
npm run package # build + zip from dist/ → tmp/vBookmarks_<version>.zip
python3 scripts/package.py --root dist # zip from an existing dist/ (no rebuild)
python3 scripts/package.py --output x.zip # custom output path
Packaging (deployment)
npm run package # 4.1.0+ default: build dist/ then zip it → tmp/vBookmarks_<version>.zip
python3 scripts/package.py --root dist # zip from an existing dist/ (no rebuild)
python3 scripts/package.py # source-root zip (dev form, 134 files — legacy/对照)
The zip is for Chrome Web Store submission. Runtime file lists live in scripts/runtime-files.json — the single source of truth shared by build.mjs and package.py (keep it in sync when adding or removing runtime files). The JS seed is classicJs + esmEntries (15 files); resolve_js_imports walks the import graph recursively (IMPORT_RE matches static from/import '…' and dynamic import('…') alike), so a module reachable only through imports — e.g. src/dropdown.js, pulled in by src/view-dupes.js — ships without being listed in source-root mode; dist bundles contain no imports, so nothing is added there (78 files). An unresolvable target prints a WARNING.
Release process (发布流程 = git发布 + 商店发布)
The release is one process with two sequential steps. git发布 prepares version / changelog / tag / package and pushes; 商店发布 uploads the packaged zip to the Chrome Web Store via the CWS API V2 and submits it for review. Store publishing requires git发布 to have been executed for the same version — enforced automatically by the pre-check in scripts/webstore/publish.js (见 Step 2)。
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 · 61 lines · 0 tokens per session scan A 4a9be969f723
release is an agent published in the GitHub repository windviki/vBookmarks (134 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,072 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
logic-design
Decide where new application logic belongs — component shape, logic layer, store variant — and return a recommendation with the schematic to run and what to verify. Use the logic-review agent for existing code.
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
doc-to-deck-agent
Converts a Pages or Word document into a Keynote slide deck.
sheet-report-agent
Analyzes spreadsheet data and produces a report with charts.
meeting-start-agent
Detects the current meeting and starts a Voice Memo recording.
sheet-convert-agent
Converts between Excel and Numbers formats.