A guided workflow for adding BeeL, an online invoicing service, to a software project. It covers client setup, configuration, and invoice-related actions such as customers, products, recurring invoices, and exports.

Use it to add BeeL billing to an existing application or implement a specific flow, such as creating invoices, issuing them, managing customers, or exporting data.

It helps avoid building against outdated or guessed API details. It also keeps retries, duplicate requests, and different programming languages in mind.

implement — Skill for Claude Code by beel-es/claude-plugins

Install

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.

Any agent

npx skills add beel-es/claude-plugins --skill implement

Clone the repo

git clone --depth 1 https://github.com/beel-es/claude-plugins

Made for: Claude Code.

Or install beel-api, the plugin that ships this one along with the rest of its 6 skills, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/beel-es/claude-plugins/implement/github.svg)](https://agentmods.dev/skills/beel-es/claude-plugins/implement)

Your own site

<a href="https://agentmods.dev/skills/beel-es/claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/beel-es/claude-plugins/implement/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/beel-es/claude-plugins/implement"><img src="https://agentmods.dev/badge/skills/beel-es/claude-plugins/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,135 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00059	$0.01135
Opus 5.5	$0.00024	$0.00454
Sonnet 5.5	$0.00012	$0.00227
Haiku 4.5	$0.00006	$0.00113

Measured 1mo ago against content hash 89942119dbf6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

implement 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.

| Node.js / TypeScript | **Official SDK** `@beel_es/sdk` — fetch the live SDK docs (find via `curl -s https://docs.beel.es/llms.txt \| grep -i sdk`) for the current API surface before writing SDK code |

plugins/beel-api/skills/implement/SKILL.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implement a BeeL Integration

Build a correct BeeL API integration in the current project. Correct means: typed where possible, idempotent, retry-safe, envelope-aware, and validated against the live API reference — never against remembered schemas. The golden rules in the beel-api skill apply throughout.

Procedure

1. Detect the stack and choose the integration path

Inspect the project (package.json, pyproject.toml/requirements.txt, go.mod, …):

Stack	Path
Node.js / TypeScript	Official SDK `@beel_es/sdk` — fetch the live SDK docs (find via `curl -s https://docs.beel.es/llms.txt \| grep -i sdk`) for the current API surface before writing SDK code
Python	Typed client generated from the OpenAPI spec — see `../beel-api/recipes/typed-client.md`
Anything else	Raw HTTP following the invariants in the `beel-api` skill

If an integration already partially exists, extend it in its style rather than introducing a second client.

2. Scope the flows

If the user named a flow (e.g. "invoice my Stripe payments", "monthly recurring invoices"), implement that. If not, ask which flows they need rather than guessing — typical ones:

Create + issue invoices (the core flow — see ../beel-api/recipes/invoice-flow.md)
Customer / product management or import (CSV, Holded)
Recurring invoices
Mark paid / send by email / PDF download
Exports (Excel, bulk PDF)
Webhook-driven reactions → hand off to /beel-api:webhooks

3. Fetch the live reference for each flow

For every endpoint you are about to call, fetch its doc page (discover via https://docs.beel.es/llms.txt) or its OpenAPI definition. Field names, required fields and enums must come from the live spec — never invented.

4. Environment setup

API key in BEEL_API_KEY env var; add to .env.example (placeholder only), never to committed files
Start against sandbox (beel_sk_test_); make the production switch a deployment concern, not a code change
Base URL is always https://app.beel.es/api — the key prefix selects the environment, there is no separate test URL. The /v1/ belongs to the path, not to the base URL: every documented path already starts with it, so configuring a generated client with /api/v1 produces /api/v1/v1/… and a uniform 404

Read the full file on GitHub · 74 lines

Changes

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 First seen · 74 lines · 59 tokens per session scan A 89942119dbf6

Subscribe to this mod's changes

implement is a skill published in the GitHub repository beel-es/claude-plugins (4 stars, last pushed 11d ago), licensed MIT. It adds 59 tokens to every session and 1,135 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.

Claude Code Finance and fintech anthropic claude compliance invoicing rgpd

regtech-expert

Expert in regulatory technology, compliance automation, KYC/AML, transaction monitoring, risk assessment, and automated reporting. Use when the user mentions compliance, KYC, AML, transaction monitoring, risk assessment, or regulatory reporting, or when the task involves KYC/AML Compliance, KYC/AML Program, Regulatory…

personamanagmentlayer/pcl · 73 tokens

ezatwork-business-assistant

Run a freelancer's or small service business's back office in EZ@Work through the EZ@Work MCP server: look up clients and projects, log billable hours, add new clients, and prepare draft invoices from logged work. Use when the user asks to "log 3 hours on ", "bill ", "draft an invoice", "add a new client", "what…

eranfinish/ezatwork-mcp · 145 tokens

implement