vBookmarks AGENTS.md

A set of instructions for coding agents working on vBookmarks, a browser extension. It provides an overview and links to detailed guidance for the repository layout, testing, releases, translations, known issues, and design rules.

In plain words
What is it for?
Use it when changing vBookmarks modules, tests, browser-extension releases, translations, documented quirks, or visual and interaction behavior.
Why use it?
It helps agents load only the detailed instructions relevant to their task and follow the project's testing and release requirements.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/windviki/vbookmarks/agents-md
Clone the repo
git clone --depth 1 https://github.com/windviki/vBookmarks

Made for: Codex, OpenCode.

Per session 5,710 This file is loaded in full into every session.
When invoked 5,710 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.05710 $0.05710
Opus 5 $0.02855 $0.02855
Sonnet 5 $0.01142 $0.01142
Haiku 4.5 $0.00571 $0.00571

Measured yesterday against content hash 3cb9d5bf73de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vBookmarks AGENTS.md 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 yesterday.

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.

AGENTS.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Guidance for AI coding agents working on this repository. Assumes no prior knowledge of the project.

Progressive disclosure: this file is the always-loaded orientation layer. Detailed references live in docs/agents/ — follow the link when a task touches that area. When a behavior contract changes, update the detail file (it is the canonical layer); touch this file only when the grouping or a summary changes.

  • docs/agents/modules.md — per-module reference (the full Repository Layout table: every src/ module, page and css file — role, behavior contracts, ctx wiring, quirks, and its test suite)
  • docs/agents/testing.md — unit-test conventions and tests/helpers/ contracts, the Docker real-browser harness (smoke/keyboard/scrollbar gates + gotchas), manual testing checklist
  • docs/agents/release.md — release build/packaging detail, the two-step release process (git发布 + 商店发布 via the CWS API)
  • docs/agents/i18n.md — locale management flow (scripts/i18n.py, translate/verify gates)
  • docs/agents/quirks.md — verified known quirks, full text
  • docs/agents/design-laws.md — the visual/interaction laws distilled from repeated user feedback (right-edge 8px axis, 20px/24px icon-column geometry, staged glyph language, two-rung selecting bars, in-place flip sync…). READ BEFORE touching toolbars, row buttons or group heads

Project Overview

vBookmarks is a Google Chrome extension (Manifest V3) that provides an enhanced bookmark manager in a toolbar popup: hierarchical bookmark tree, in-popup and omnibox search, context menus, keyboard navigation, drag & drop, bookmark separators, and bookmark sync-status indicators. It is a fork/successor of Neat Bookmarks, maintained by windviki and distributed via the Chrome Web Store. Licensed under MIT (license.txt).

  • Current version: 4.1.0 (see manifest.json; package.json tracks the same version for dev tooling)
  • Minimum Chrome version: 114 (Manifest V3)
  • Tech stack: plain ES6+ JavaScript — no framework, no bundler, no dev build step. The repository root is the extension root (what "Load unpacked" points at). Since 4.1.0 the release is built and packaged from dist/ (npm run buildnpm run package; see docs/plan-4.1.0/build-and-performance-plan.md) — dev stays build-free.

Read the full file on GitHub · 123 lines

Changes

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.

  1. yesterday First seen · 123 lines · 5,710 tokens per session scan A 3cb9d5bf73de

Subscribe to this mod's changes

vBookmarks AGENTS.md is an instructions file published in the GitHub repository windviki/vBookmarks (133 stars, last pushed 2d ago), licensed MIT. It adds 5,710 tokens to every session, about $0.0285 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.