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.00091 | $0.01448 |
| Opus 5 | $0.00046 | $0.00724 |
| Sonnet 5 | $0.00018 | $0.00290 |
| Haiku 4.5 | $0.00009 | $0.00145 |
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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alef-Generated Bindings
Files under packages/*/ and in the binding crates are generated by Alef — do not hand-edit.
Workflow
- Check
alef.tomlbefore touching anything inpackages/*/or a binding crate - Modify the Rust source or
alef.tomlitself task alef:generate→alef all --clean. This formats via poly as part of the run; there is notask alef:formattask alef:verify→alef verify --exit-codetask e2e:generatethentask e2e:test(ortask e2e:all) to verify behaviour- Commit Rust source +
alef.toml+ regenerated output atomically
The alef:* namespace is exactly: generate, verify, build, sync, docs,
verify:readme-paths, verify:ffi-formats. Formatting is poly fmt / poly lint.
Freshness check
task 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/.
Alef tracks both sides under .alef/: sources_hash.cache (input hashes over the parsed
Rust sources) and .alef/hashes/xberg.<lang>.output_hashes (per-file output content hashes).
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 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.
- 9d 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,275 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 1,448 once invoked, about $0.0005 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
composio
Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help…
live-tutorial
Create an annotated MP4 tutorial from a workflow demonstrated in the owner's actual application. Use when asked for a tutorial video, not merely to watch an action live.
docs-decisions
Work on Composio documentation content, Fumadocs configuration, changelogs, docs automation prompts, docs decisions, ADR-style records, and docs review guidance. Use for files under docs/, documentation workflows, or requests to record or update a docs decision. Do not use for SDK runtime changes unless docs are the…
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.