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/beel-es/claude-plugins/multi-nifnpx skills add beel-es/claude-plugins --skill multi-nifgit 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/multi-nif)<a href="https://agentmods.dev/skills/beel-es/claude-plugins/multi-nif"><img src="https://agentmods.dev/badge/skills/beel-es/claude-plugins/multi-nif.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.00092 | $0.02130 |
| Opus 5 | $0.00046 | $0.01065 |
| Sonnet 5 | $0.00018 | $0.00426 |
| Haiku 4.5 | $0.00009 | $0.00213 |
Grade A, and why
multi-nif 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 4d 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 https://app.beel.es/api/v1/invoices \ How it starts
The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BeeL Multi-NIF — Integration Guide
BeeL's multi-NIF model lets one account (one API key) hold many companies, each a Spanish tax ID (NIF/CIF) with its own fully isolated invoices, customers, products and series. Built for professionals with several NIFs, agencies (gestorías) and fleets that invoice on behalf of the businesses they manage.
The golden rules in the beel-api skill apply throughout — especially: never
invent endpoints, fields or scopes; verify against the live docs.
The model (know this before writing code)
| Concept | What it is |
|---|---|
| Account | The tenant you authenticate as. One API key = one account. Owns billing/auth and holds 1..N companies. |
| Company | One fiscal identity (NIF/CIF). Isolated space: its own invoices, customers, products, series — per environment (TEST/PROD). |
| Member | A person with access to the account. Account role OWNER/ADMIN (reach every company) or MEMBER (only companies granted to it, at access level VIEW or OPERATE). |
| Managed account | Another account a provisioner (agency/fleet) creates and operates on behalf of its holder, at an access level it controls: NONE, VIEW or OPERATE. |
access_level is one single vocabulary — NONE (no visibility), VIEW
(read-only), OPERATE (read and write) — used both for a member's grant over a
company and for a provisioner's access over a managed account. It never decides
who pays: billing follows the provisioning relationship, not the access level.
Members vs managed accounts — pick the right one
Both give access to operate a business, but point in opposite directions. Don't require both scopes — an integration uses one model:
- Members (
members:*) — a person joins an account that already exists. The owner, billing and NIF stay with that account; the invitee only needs a login (not an account of their own) and does no fiscal onboarding. Use when the client signed up and pays themselves and invites you in. - Managed accounts (
accounts:write) — you create and run a third party's account (its own NIF, its own billing) and they can later claim it. Use when you onboard them by API and you pay (fleets, mass onboarding, platform gestorías whose clients aren't on BeeL yet).
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.
- 4d ago First seen · 162 lines · 92 tokens per session scan A 2696da59300c
multi-nif is a skill published in the GitHub repository beel-es/claude-plugins (4 stars, last pushed 9d ago), licensed MIT. It adds 92 tokens to every session and 2,130 once invoked, about $0.0005 per session on Opus 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
tax-calculator
Calculate tax implications of trades and generate tax reports.
starknet-tongo
Confidential ERC20 payments on Starknet using Tongo protocol. Fund, transfer, withdraw, and rollover encrypted token balances with zero-knowledge proofs. Use when the user needs privacy-preserving transactions, confidential payments, encrypted balances, or auditable private transfers on Starknet.
invoicing
Use when issuing an invoice, quote, or credit note and moving it draft-to-paid — the legally required VAT fields, gap-free numbering, per-country e-invoicing mandates, dunning overdue ones. NOT recording a paid invoice in the books (that is bookkeeping), NOT Stripe SDK plumbing (that is stripe), NOT setting the price…
expense-report
Generate a detailed expense breakdown by category for a given period. Use when the user asks for an expense report, spending summary, Ausgabenübersicht, cost analysis, or wants to understand where their money is going.
fee-billing
Build and manage advisory fee billing operations from fee schedule design through calculation, collection, revenue recognition, and compliance disclosure. Use when the user asks about tiered or breakpoint fee schedules, billing cycle configuration, AUM valuation for billing, direct-debit vs invoice collection, GAAP…
stp-automation
Measure and raise straight-through processing (STP) rates in securities operations through zero-touch, exception-based processing. Use when measuring STP rates and analyzing manual touchpoints in an existing process, replacing review-all workflows with exception-based processing, evaluating RPA vs API-based vs hybrid…