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 themesic/perfex-rest-api-examples --skill perfex-sales-documentsgit clone --depth 1 https://github.com/themesic/perfex-rest-api-examplesWrote 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/themesic/perfex-rest-api-examples/perfex-sales-documents)<a href="https://agentmods.dev/skills/themesic/perfex-rest-api-examples/perfex-sales-documents"><img src="https://agentmods.dev/badge/skills/themesic/perfex-rest-api-examples/perfex-sales-documents/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/themesic/perfex-rest-api-examples/perfex-sales-documents"><img src="https://agentmods.dev/badge/skills/themesic/perfex-rest-api-examples/perfex-sales-documents.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.00074 | $0.00672 |
| Opus 5.5 | $0.00030 | $0.00269 |
| Sonnet 5.5 | $0.00015 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
perfex-sales-documents 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 7d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perfex CRM sales documents
Invoices, estimates, proposals and credit notes carry line items. These tools follow the {resource}_{action} pattern (for example invoices_create, estimates_get, proposals_update, credit_notes_list, payments_list). Follow the general perfex-crm skill for lookups, confirmations and error handling; this skill adds the document-specific rules.
Before creating a document
- Resolve the customer with
customers_searchand use its id (clientid). Ask if the match is ambiguous. - Get the currency id from
list_currenciesand, if the user mentions tax, the tax names or ids fromlist_taxes. Do not invent ids. - Use
get_current_datetimefor today's date and for due dates expressed relatively ("net 30"). - For catalog products or services, look them up with
items_searchand reuse their description and rate. - Show the user a draft (customer, date, due date, currency, each line with quantity, rate and line total, and the expected subtotal) and confirm before calling
_create.
Line items
- Pass line items in
data.itemsas an array of objects withdescription, optionallong_description,qty,rate, and optionalunit. Subtotal and total are calculated by the CRM from the items. {resource}_getreturns the current line items in anitemsarray, each with itsitemid.- On
{resource}_update, includeitemidto edit an existing line, omititemidto add a new line, and list theitemids to remove in aremoved_itemsarray. Fields you leave out ofdataare not changed. - Always read the document with
_getbefore editing its lines so you work from the current items.
Payments
- Find payments with
payments_listorpayments_search; read the related invoice withinvoices_getwhen you need the balance or status. - Recording or changing a payment only updates the CRM's records. It never moves money. Confirm amount, date, payment mode (from
list_payment_modes) and invoice before writing.
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.
- 7d ago First seen · 40 lines · 74 tokens per session scan A 2647a015a074
perfex-sales-documents is a skill published in the GitHub repository themesic/perfex-rest-api-examples (5 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 672 once invoked, about $0.0003 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-10-09.
Other skills, from other repositories
alpaca-trade-api-sdk
Integrate and build on the @alpacahq/alpaca-trade-api TypeScript SDK for the Alpaca Trading and Market Data APIs (the unified Alpaca client, ergonomic order builders, normalized market-data shapes, pagination, typed errors, resilience, and real-time streaming). Use when writing or reviewing code that imports…
hero-invoice-total
A clean invoice reveals three line items, then counts the total to $610. Function: billing / paid receipt.
hero-transfer-flow
A green value packet travels the rail while balances debit and credit live. Function: payout / transfer / fintech move.
starter-dashboard
Scaffold a local Next.js Alpaca dashboard using the published @alpacahq/alpaca-trade-api SDK for paper Trading API and Market Data API workflows. Use when the user asks for starter-dashboard, a starter Alpaca dashboard, a local Trading API demo, a Market Data API dashboard, or a greenfield Next.js Alpaca SDK prototype.
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…
modeling-revenue-metrics
Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute recurring revenue, monthly/annual recurring…