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 skills/causify-ai/helpers/bookmark.addnpx skills add causify-ai/helpers --skill bookmark.addgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/skills/causify-ai/helpers/bookmark.add)<a href="https://agentmods.dev/skills/causify-ai/helpers/bookmark.add"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/bookmark.add.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 | $0.00015 | $0.00512 |
| Opus 5 | $0.00008 | $0.00256 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
bookmark.add 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 5d 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
Goal
- Given one or more links
<LINKS>, find which file(s) among the following are related to each link, and add a TODO to the most related file:research/ideas/*.mdwebsite/docs/blog/posts/*.md
// TODO(gp): incorporate the link <LINK> to <TOPIC>
Workflow
Step 1: Collect Material
- Read the title / content of each link in
<LINKS>(useWebFetchif the URL alone is not descriptive enough to judge topic) - List all candidate files:
research/ideas/*.mdwebsite/docs/blog/posts/*.md
Step 2: Match Links to Files
- For each link, compare its topic against the content of each candidate file (title, headers, first paragraph) and rank candidates by relevance
- Pick the single best-matching file for each link
- If several files are close in relevance, list them and ask the user which one to use
- If no file is a plausible match (topic not covered anywhere), do not force a match: report this to the user instead of guessing
Step 3: Add the TODO
- In the matched file, add one line:
where// TODO(gp): incorporate the link <LINK> to <TOPIC><TOPIC>is a short (< 15 words) description of what part of the link is relevant (e.g., a technique, a result, a quote) - Placement:
- If the file already has a top-of-file
// TODO(gp): ...block, add the new TODO as an adjacent line in that block - Otherwise, add it near the section of the file the link is most related to (e.g., right above the relevant bullet point or paragraph)
- If the file already has a top-of-file
- Do not change any other content of the file
- If multiple links map to the same file, add one TODO line per link
Step 4: Report
- Print, for each link, which file it was added to and the exact TODO line that was inserted
- For any link that could not be matched, report that explicitly instead of silently skipping it
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.
- 5d ago First seen · 52 lines · 15 tokens per session scan A 8ab6a05f47e3
bookmark.add is a skill published in the GitHub repository causify-ai/helpers (145 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 512 once invoked, about $0.0001 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…