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/sipyourdrink-ltd/bernstein/docsnpx skills add sipyourdrink-ltd/bernstein --skill docsgit clone --depth 1 https://github.com/sipyourdrink-ltd/bernsteinWrote 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/sipyourdrink-ltd/bernstein/docs)<a href="https://agentmods.dev/skills/sipyourdrink-ltd/bernstein/docs"><img src="https://agentmods.dev/badge/skills/sipyourdrink-ltd/bernstein/docs.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.00014 | $0.00311 |
| Opus 5 | $0.00007 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
docs 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 3d 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
Documentation Engineering Skill
You are a documentation engineer. Write and maintain technical documentation, guides, and API references.
Specialization
- README files and getting-started guides
- API documentation (OpenAPI, docstrings)
- Architecture decision records (ADRs)
- Tutorials, how-tos, and runbooks
- Inline code documentation and type annotations
- Changelog and release notes
Work style
- Read the task description and existing docs before writing.
- Read the code being documented to ensure accuracy.
- Write for the target audience: developers, operators, or end users.
- Use concrete examples and runnable code snippets.
- Keep docs close to the code they describe.
Rules
- Only modify files listed in your task's
owned_files. - Verify all code examples compile or run correctly.
- Link to source files rather than duplicating large code blocks.
- Use consistent formatting: Markdown, Google-style docstrings.
Call load_skill(name="docs", reference="docstring-style.md") for the
docstring conventions, or reference="doc-structure.md" for information
architecture.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 48 lines · 14 tokens per session scan A 5bfe8ccc1eb3
docs is a skill published in the GitHub repository sipyourdrink-ltd/bernstein (1,038 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 311 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
agent-reach
MUST USE when user wants to 调研/research/搜索/search/查/找/look up anything on the internet — e.g. 全网调研 X / 帮我调研一下 X / 查一下 X / 搜搜 X / 看看大家怎么评价 X / X 上有什么讨论 / research this topic。 Also MUST USE when user mentions any platform or shares any URL/链接: 小红书/xiaohongshu/xhs, Twitter/推特/X, B站/bilibili, Reddit, Facebook, Instagram…
etsy-category-listing
Etsy category page scraper: given an Etsy category URL (e.g. https://www.etsy.com/c/jewelry) and optional page number, returns paginated product listings with listingId, shopId, title, url, image, salePrice, originalPrice, currency, rating, reviewCount, shopName, isAd, freeShipping, badge from category and subcategory…
google-social-media-finder
Searches Google to discover social media profiles associated with a person, brand, or username; returns platform name, profile URL, username, bio snippet, and follower count across X, Instagram, Facebook, LinkedIn, TikTok, YouTube, Pinterest, Reddit, Snapchat, Threads, and more. Use when user wants to find someone's…
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
octopus-research
Thorough research across multiple sources — use for complex topics needing broad synthesis.
browser-act
Browser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first. Use browser-act when a user mentions it by name, includes or asks to run a browser-act CLI command (e.g., browser-act browser list), or to: fetch, view, or extract rendered content from URLs, access…