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 akiotanaka847/qaio-desktop --skill check-my-sales-tax-nexusgit clone --depth 1 https://github.com/akiotanaka847/qaio-desktopWrote 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/akiotanaka847/qaio-desktop/check-my-sales-tax-nexus)<a href="https://agentmods.dev/skills/akiotanaka847/qaio-desktop/check-my-sales-tax-nexus"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/check-my-sales-tax-nexus/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/akiotanaka847/qaio-desktop/check-my-sales-tax-nexus"><img src="https://agentmods.dev/badge/skills/akiotanaka847/qaio-desktop/check-my-sales-tax-nexus.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.00123 | $0.01868 |
| Opus 5 | $0.00062 | $0.00934 |
| Sonnet 5 | $0.00025 | $0.00374 |
| Haiku 4.5 | $0.00012 | $0.00187 |
Grade A, and why
check-my-sales-tax-nexus 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 12d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check My Sales Tax Nexus
State-by-state economic-nexus check. I total revenue and transactions per US state for the period, compare against each state's threshold, pinpoint the crossing month, and flag physical-nexus triggers (employees, offices, inventory) regardless of revenue. Exposure is ranked highest-dollar first; the three closest pre-crossing states show up as early warnings. I never register and I never remit.
When to use
- "where do we owe sales tax" / "nexus check" / "sales-tax exposure by state".
- Quarterly - end of fiscal quarter.
- Company cross round-number revenue mark ($500K, $1M, $5M) or add employees in new state.
Connections I need
I run external work through Composio. Before this skill runs I check that the categories below are linked. Missing → I name the category, ask you to connect it from the Integrations tab, stop.
- Stripe (billing) — required to pull charges with billing / shipping state for revenue-by-state aggregation. Required if Stripe is your primary contract source.
- QuickBooks Online or Xero (accounting) — pulls invoice / customer state tags as a fallback or supplement to Stripe. Optional.
If none of the required categories are connected I stop and ask you to connect Stripe first, since most startups invoice through it.
Information I need
I read your bookkeeping context first. For every required field that's missing I ask ONE plain-language question (best modality: connected app > file drop > URL > paste) and wait.
- Your company's home state — Required. Why: physical-nexus baseline; you owe sales tax there regardless of revenue. If missing I ask: "What state is the company headquartered or incorporated in?"
- How you bill customers and where contracts live — Required. Why: drives the source I use for revenue-by-state. If missing I ask: "How do you invoice customers, mostly through Stripe, through QuickBooks or Xero, or somewhere else?"
- States you already collect or file sales tax in — Optional. Why: lets me mark already-registered states as "no action" instead of "new exposure." If missing I ask: "Are you already registered to collect sales tax anywhere? If you don't have it I keep going and flag every crossing as new."
- Where your employees physically work — Optional. Why: any W-2 employee in a state creates physical nexus regardless of revenue. If missing I ask: "Do you have employees working in states besides the headquarters state? If you don't have it I note it as TBD and call out physical-nexus checks for the user to confirm."
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.
- 12d ago First seen · 102 lines · 123 tokens per session scan A a9779c6a71f8
check-my-sales-tax-nexus is a skill published in the GitHub repository akiotanaka847/qaio-desktop (2 stars, last pushed 8d ago), licensed MIT. It adds 123 tokens to every session and 1,868 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-08-31.
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.
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.
invoice-system
A reference and guidance skill for Japan’s invoice system, the tax-document rules that determine when a business can claim credit for consumption tax paid on purchases. It covers qualified invoices, registration numbers, exceptions, and transitional rules.
tax-invoice-credit-context
Background rules for Japanese input-tax-credit treatment under the invoice system, including required records, exceptions, transition rates, and storage periods.
tax-housing-loan-context
Background rules for Japan’s housing-loan tax credit, including eligibility, credit limits, calculation rules, and its relationship with hometown donations.