Xberg is a document-intelligence engine that reads files, URLs, archives, and source trees and extracts text, metadata, images, tables, and structured data, with additional code-language understanding. Developers use it through language bindings, a command-line tool, REST API, or MCP server, and the catalogue entries support those integrations.
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 xberg-io/xberg --skill alef-generated-bindingsgit clone --depth 1 https://github.com/xberg-io/xbergWrote 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/xberg-io/xberg/alef-generated-bindings)<a href="https://agentmods.dev/skills/xberg-io/xberg/alef-generated-bindings"><img src="https://agentmods.dev/badge/skills/xberg-io/xberg/alef-generated-bindings/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/xberg-io/xberg/alef-generated-bindings"><img src="https://agentmods.dev/badge/skills/xberg-io/xberg/alef-generated-bindings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.01435 |
| Opus 5.5 | $0.00007 | $0.00574 |
| Sonnet 5.5 | $0.00003 | $0.00287 |
| Haiku 4.5 | $0.00002 | $0.00144 |
Grade A, and why
alef-generated-bindings 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alef-Generated Bindings
Xberg specifics on top of the shared Alef workflow skill (generic regenerate/verify/commit loop).
- Check
alef.tomlbefore touching anything inpackages/*/or a binding crate. - Regenerate with
alef all --clean --skip-compile --skip-snippet-validation(aftermise run dart:format:context); it formats via poly. There is noalef:generateoralef:formattask. mise run alef:verifyrunsalef verify --exit-code.- Run
alef docsdirectly to generate API documentation. - The
alef:*namespace is exactly:verify,build,verify:readme-paths,verify:ffi-formats,verify:fields.
Freshness check
mise run alef:verify. A hand-rolled git diff over packages/ is under-scoped — generated
output also lands in crates/xberg-py/, crates/xberg-php/, crates/xberg-jni/,
crates/xberg-node/, crates/xberg-wasm/, crates/xberg-ffi/, packages/dart/rust/,
packages/swift/rust/, and e2e/.
Each generated file carries an // alef:hash: header that alef verify recomputes; .alef/
(sources_hash.cache, hashes/) is a gitignored local cache, empty in a new worktree.
Neither makes a generated file safe to hand-fix — a regen restores it. Fix alef.toml or the
Rust source, then regenerate and re-verify.
Key alef.toml sections
[workspace],[workspace.sync](version-syncextra_paths),[workspace.docs],[workspace.poly],[workspace.generate][[crates]]— the Rust source crate parsed for type/function extraction, plus[[crates.source_crates]][crates.<lang>]— one table per binding:python,node,ruby,php,elixir,wasm,ffi,go,java,dart,kotlin_android,jni,swift,csharp,zig(each carryingexclude_functions,target_dep_overrides, stubs, …)[crates.e2e]— e2e generation (output = "e2e",[crates.e2e.call.overrides.<lang>])[crates.readme]— README generation (template_dir = "templates/readme",[crates.readme.languages.<lang>])[crates.exclude],[crates.output],[crates.custom_modules],[crates.publish]
What ships with it
1 file 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.
- yesterday Changed · +1 lines · -18 tokens per session c4e3d1d7808f
- 2d ago Changed · +1 lines ee65bb1aea19
- 4d ago Changed · -16 tokens per session aacc9190b5b5
- 5d ago Changed · +2 lines · -34 tokens per session 08f8167ecf15
- 20d ago Changed · +6 lines · -6 tokens per session 3529829ef77b
- 2mo ago First seen · 92 lines · 91 tokens per session scan A ec08fcd69a78
alef-generated-bindings is a skill published in the GitHub repository xberg-io/xberg (9,497 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 1,435 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-08-30.
Other skills, from other repositories
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
first-reader
Beta readers for any draft, run by simulating how a real reader experiences it, moment by moment. A skim gate, a no-lookahead timed read producing an attention transcript with quit points, a recall test of what a reader remembers the next day, and a trust ledger of the implied author. Use when the user asks for a beta…
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-cli
Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0…
mem0-remember
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.