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 beel-es/claude-plugins --skill beel-apigit clone --depth 1 https://github.com/beel-es/claude-pluginsWrote 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/beel-es/claude-plugins/beel-api)<a href="https://agentmods.dev/skills/beel-es/claude-plugins/beel-api"><img src="https://agentmods.dev/badge/skills/beel-es/claude-plugins/beel-api/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/beel-es/claude-plugins/beel-api"><img src="https://agentmods.dev/badge/skills/beel-es/claude-plugins/beel-api.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.00040 | $0.01342 |
| Opus 5.5 | $0.00016 | $0.00537 |
| Sonnet 5.5 | $0.00008 | $0.00268 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
beel-api scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://docs.beel.es/llms.txt | grep -i "invoice\|customer" How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BeeL API — Integration Guide
BeeL is a SaaS invoicing platform for Spanish autónomos with full VeriFactu compliance.
⚠️ Golden Rules
- NEVER invent endpoints, fields, or package names. Always verify against the live docs first — see "How to Look Up Documentation" below for the token-efficient way to do it.
- NEVER hardcode API keys. Always use environment variables (
process.env.BEEL_API_KEY). - There is NO separate test URL. Base URL is always
https://app.beel.es/api, and every path starts with/v1/. The key prefix determines the environment:beel_sk_test_*= sandbox,beel_sk_live_*= production. - Company-scoped paths are the canonical form. Build new code against
/v1/companies/{company_id}/…(invoices, customers, products, series, tax and VeriFactu settings). The flat routes (/v1/invoices,/v1/customers,/v1/products,/v1/configuration/*and their sub-paths like/issueand/void) aredeprecated: true, each carrying anx-successor; they keep working until the date in theirSunsetresponse header. BeeL-Active-Companyis only for the flat routes. A company-scoped path names its target, and the header is not read there at all. On a flat route it carries thecompany_id: optional on an account with a single NIF, required on an account with several — otherwise403 ACTIVE_COMPANY_REQUIRED. Following rule 4 means you never need it. See/beel-api:multi-nif.Idempotency-Keyon POST. Ignored on PUT/PATCH/DELETE unless the operation opts in. Optional in general, required on bulk imports. See recipes/invoice-flow.md.- Issued invoices are immutable. To correct → corrective invoice. To cancel → void it.
- When in doubt, look up the docs (see below).
📚 How to Look Up Documentation
Preferred: the BeeL CLI docs search — and propose it to the user first.
When you need to check the docs, don't silently fetch the whole llms.txt / llms-full.txt (that burns tokens and pulls in ~600KB you don't need). Instead, suggest running the CLI and wait for the user's go-ahead, e.g.:
What ships with it
6 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.
- 1mo ago Changed 4e881e98d506
- 1mo ago First seen · 85 lines · 40 tokens per session scan A f0721d1d1ce1
beel-api is a skill published in the GitHub repository beel-es/claude-plugins (4 stars, last pushed 11d ago), licensed MIT. It adds 40 tokens to every session and 1,342 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
standards-expert
Expert-level ISO standards, quality management, compliance, and certification. Use when the user mentions ISO standards, quality management, compliance, or certification, or when the task involves Compliance & Certification, Auditing, or Continuous Improvement.
gdpr-expert
Expert in GDPR compliance, data protection, privacy by design, consent management, DPO responsibilities, and EU data regulations. Use when the user mentions privacy, data protection, compliance, consent, a DPO, or eu regulation, or when the task involves GDPR Fundamentals, Key Principles, Data Subject Rights, or…
soc2-expert
Expert in SOC 2 compliance, trust service criteria, audit preparation, controls implementation, and security frameworks. Use when the user mentions compliance, audit, trust services, AICPA, controls, or security framework, or when the task involves Trust Service Criteria, SOC 2 Types, Security Common Criteria, or…
lawyer-expert
Expert-level legal systems, contracts, compliance, and legal technology. Use when the user mentions legal, contracts, compliance, law, or legal tech, or when the task involves Legal Systems, Legal Technology, Compliance Frameworks, or Contract Management.
audit-expert
Expert-level security auditing, compliance, code review, and vulnerability assessment. Use when the user mentions compliance, security review, code review, vulnerability assessment, SOC 2, or GDPR, or when the task involves Audit Types, Audit Frameworks, Audit Process, or Authentication Review.
legaltech-expert
Expert in legal technology: contract lifecycle management, e-discovery, AI-assisted legal research, case and matter management, document automation, and compliance tooling. Use when the user mentions legal case or matter management, e-discovery and legal holds, CLM or contract review and obligation tracking, legal…