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 joaoguirunas/team-os --skill finance-receivables-payablesgit clone --depth 1 https://github.com/joaoguirunas/team-osWrote 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/joaoguirunas/team-os/finance-receivables-payables)<a href="https://agentmods.dev/skills/joaoguirunas/team-os/finance-receivables-payables"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/finance-receivables-payables/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/joaoguirunas/team-os/finance-receivables-payables"><img src="https://agentmods.dev/badge/skills/joaoguirunas/team-os/finance-receivables-payables.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.00099 | $0.02105 |
| Opus 5.5 | $0.00040 | $0.00842 |
| Sonnet 5.5 | $0.00020 | $0.00421 |
| Haiku 4.5 | $0.00010 | $0.00211 |
Grade A, and why
finance-receivables-payables 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 20d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finance Receivables & Payables — a squad prepara, o humano executa
Dinheiro sai e entra por atos que não se desfazem: um PIX, um boleto pago, uma nota emitida, uma cobrança enviada. Este método existe para que tudo o que antecede esse ato — valor, documento, destinatário, prioridade, texto — chegue pronto e conferido, e para que o ato em si seja sempre do usuário, com PASS de TIGRE e confirmação explícita para este lote ou esta cobrança.
1. Princípios
- A squad prepara o lote/cobrança; o humano executa. Pagamento, transferência, PIX, boleto, emissão de NF e envio de cobrança ao cliente são executados pelo usuário (ou pelo sistema que ele opera), só com PASS de TIGRE + confirmação explícita do usuário para este lote/esta cobrança. Agendar no banco é executar.
- Todo valor vem de
#id. Cobrança cita o#idda receita/contrato no fechamento; pagamento cita o#iddo documento lançado. Sem#id, não há item. - Nunca alterar valor aprovado. Desconto, parcelamento, juros perdoados são decisão de AMAZONAS/usuário, registrada antes de entrar na cobrança.
- Alçada define quem aprova o item; não dispensa PASS nem confirmação para executar.
- Confirmação não se herda. "O usuário confirmou o lote de ontem" não vale para o de hoje. Um lote, uma confirmação, com data e texto.
- Beneficiário e pagador por alias. Conta bancária, chave PIX e CPF/CNPJ completo nunca vão a template nem smart-memory; ficam no sistema do usuário.
- Toda interação registrada. Cobrança enviada, resposta, promessa de pagamento, negociação — linha no ledger com data e autor.
2. Contas a receber
2.1 Ledger (receivables.md)
| Cliente (alias) | #id | Documento (contrato/NF) | Emissão | Vencimento | Valor | Status | Régua (último passo, data) | Próximo passo | Data |
Status: a emitir · emitido · a vencer · vencido · negociado · recebido (#lanc) · perdido (decisão). recebido só com par na conciliação de GANGES.
2.2 Emissão preparada
Pacote por cobrança: cliente (alias), #id, descrição conforme contrato, valor, vencimento (regra do contrato), forma de pagamento (do contrato — sem dados bancários no pacote), texto da mensagem (template). Emissão de NF e envio → usuário, após PASS + confirmação.
What ships with it
3 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.
- 20d ago Changed · -34 tokens per session c64086c1836c
- 25d ago First seen · 97 lines · 133 tokens per session scan A a1fa174fc107
finance-receivables-payables is a skill published in the GitHub repository joaoguirunas/team-os (4 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 2,105 once invoked, about $0.0004 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-09-21.
Other skills, from other repositories
comps-analysis
Build comparable-company valuation workbooks in Excel.
polymarket
Query Polymarket: markets, prices, orderbooks, history.
portfolio-review
A workflow for researching companies and managing a group of investments. It uses shared research rules and checks the date and data sources before reporting.
polymarket-trading
Use when the user wants to actually PLACE, manage, or redeem bets on Polymarket (not just read odds — that's the blockrunpredexon data tools). Covers setup (deposit wallet, funding, approvals), buy/sell with confirm gating, positions, redeeming winnings, geoblock handling, and the end-to-end flow.
price-alert
Fire when the tracked token does something - new ATH, sharp 1h move, or operator-set target crossed. Silent on normal days.
unlock-monitor
Token unlock and vesting tracker - quantify supply pressure via absorption ratio, classify cliff vs linear, and deliver one-line market reads.