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 Hainrixz/agente-pagokit --skill tax-advisorgit clone --depth 1 https://github.com/Hainrixz/agente-pagokitWrote 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/hainrixz/agente-pagokit/tax-advisor)<a href="https://agentmods.dev/skills/hainrixz/agente-pagokit/tax-advisor"><img src="https://agentmods.dev/badge/skills/hainrixz/agente-pagokit/tax-advisor/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/hainrixz/agente-pagokit/tax-advisor"><img src="https://agentmods.dev/badge/skills/hainrixz/agente-pagokit/tax-advisor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 92 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00120 | $0.01203 |
| Opus 5 | $0.00060 | $0.00602 |
| Sonnet 5 | $0.00024 | $0.00241 |
| Haiku 4.5 | $0.00012 | $0.00120 |
Grade A, and why
tax-advisor 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 8d 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.
tax-advisor
A successful payment is not a compliant sale. This skill covers the gap.
The distinction that matters most
Two entirely different questions get conflated:
- Who collects and remits the tax? — the merchant-of-record question.
- Who issues the fiscal document? — the e-invoicing question.
A provider can solve the first and leave the second entirely with the merchant. In Mexico and Brazil, the second one is a legal obligation attached to the sale, and it is the one that gets forgotten because the payment works fine without it.
Merchant of record: what you actually trade
Read mor from the provider entry. When is_mor is true, that provider sells to your
customer. You sell to the provider.
| You gain | You give up |
|---|---|
| Tax registration, collection, remittance and filing in every market it covers | 4-6% more per transaction than a direct processor |
| No VAT thresholds to monitor, no OSS filing, no nexus tracking | Their name on the customer's bank statement, not yours |
| Chargebacks and fraud are their problem | Checkout branding, and often the customer relationship |
| Invoices issued for you | Payout on their schedule — often 14-30 days |
| No entity needed in the markets they cover | Whatever mor.disables_capabilities lists |
The trade is worth it far more often than developers assume, and it is almost always worth it for a solo developer selling digital goods across borders. Registering for VAT in seven EU countries is not a thing one person does alongside building a product.
It is usually not worth it for a domestic business selling in its own market, where it already has an accountant and pays domestic interchange.
E-invoicing: the obligation nobody generates code for
Read regions[CODE].tax.einvoice from the catalog. Where a mandate exists, the merchant must
issue a specific fiscal document for each sale, in a specific format, within a specific window.
The part that bites: the data must be collected at checkout. You cannot retro-fit an RFC, a CNPJ or a tax ID after the sale — the customer has gone. If the market mandates e-invoicing and the checkout does not collect the identifier, every sale is already non-compliant.
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.
- 8d ago First seen · 97 lines · 120 tokens per session scan A 3061ce9e1eee
tax-advisor is a skill published in the GitHub repository Hainrixz/agente-pagokit (50 stars, last pushed 12d ago), licensed MIT. It adds 120 tokens to every session and 1,203 once invoked, about $0.0006 per session on Opus 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-04.
Other skills, from other repositories
assess
A Japanese tax-filing assessment guide that asks about your income, family, and business situation to identify which tax returns you may need.
e-bookkeeping-compliance
A compliance checker for Japan's rules on keeping high-quality electronic accounting books. It checks whether accounting records and related documentation meet specified requirements for electronic storage.
internal-controls-and-audit
Designs and tests controls over financial reporting — segregation of duties, approval limits, evidence, and preparing for audit. Use this to design controls for a process, prepare for an external audit, respond to an audit finding, set approval thresholds, or assess where a small team's segregation of duties is…
incorporation
A guide for moving from working as an individual business owner to operating through a company in Japan. It covers company types, setup steps, officer pay, taxes, and social insurance.
capital-structure-and-covenants
Decides how the business is financed and what that financing then requires of it — debt versus equity, weighted average cost of capital as a hurdle rate, how much leverage cash flow can carry, and the financial, affirmative and negative covenants, definitions, test dates and cure rights that come attached. Use this to…
revenue-recognition
Determines when and how revenue is recognized — performance obligations, contract terms that change the answer, and the deal structures that create accounting problems. Use this to work out how a contract should be recognized, review a non-standard deal before it is signed, understand deferred revenue, or spot terms…