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 skills add CHENyiru3/AI-Skills-Collections --skill bitwardengit clone --depth 1 https://github.com/CHENyiru3/AI-Skills-CollectionsWrote 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/chenyiru3/ai-skills-collections/bitwarden)<a href="https://agentmods.dev/skills/chenyiru3/ai-skills-collections/bitwarden"><img src="https://agentmods.dev/badge/skills/chenyiru3/ai-skills-collections/bitwarden/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chenyiru3/ai-skills-collections/bitwarden"><img src="https://agentmods.dev/badge/skills/chenyiru3/ai-skills-collections/bitwarden.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00275 |
| Opus 5.5 | $0.00014 | $0.00110 |
| Sonnet 5.5 | $0.00007 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
bitwarden 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 6d 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
Bitwarden CLI Skill
Headless Bitwarden CLI usage — no tmux, no interactive prompts needed.
Install
npm install -g @bitwarden/cli
# or: brew install bitwarden-cli
Verify:
bw --version
Headless Login / Unlock
Use --passwordenv to pass the master password as an environment variable.
# Login (if not already logged in)
bw login [email protected] --passwordenv BITWARDEN_PASSWORD
# Check status
bw status
# Unlock vault
export BW_SESSION=$(bw unlock --passwordenv BITWARDEN_PASSWORD --raw)
Read Secrets
bw get password "Item Name"
bw get username "Item Name"
bw get item "Item Name"
bw list items --search "query"
Security Notes
- Never echo secrets in output visible to users
- BW_SESSION expires on lock/logout
- Re-unlock with
bw unlock --passwordenv BITWARDEN_PASSWORD --rawif locked
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.
- 6d ago First seen · 54 lines · 34 tokens per session scan A 89d084c4bd05
bitwarden is a skill published in the GitHub repository CHENyiru3/AI-Skills-Collections (1 stars, last pushed 7d ago), licensed MIT. It adds 34 tokens to every session and 275 once invoked, about $0.0001 per session on Opus 5.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-10-02.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…