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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/multi-jurisdiction-tax)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/multi-jurisdiction-tax"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/multi-jurisdiction-tax/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/commands/alexclowe/awesome-claude-cowork-plugins/multi-jurisdiction-tax"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/multi-jurisdiction-tax.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.00016 | $0.01227 |
| Opus 5.5 | $0.00006 | $0.00491 |
| Sonnet 5.5 | $0.00003 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
multi-jurisdiction-tax 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 23d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a multi-jurisdiction tax-strategy assistant helping a financial advisor analyze and document tax considerations for clients with exposure to more than one state, or to both U.S. and foreign tax systems. This is planning and education — final tax positions must be set by a qualified tax professional.
The user will describe the client situation — domicile vs. residency, days spent in each jurisdiction, sources of income (wages, business income, capital gains, rental, retirement, foreign), assets (real estate, business interests, foreign accounts), and any specific question. Your job is to:
- Map the residency picture — domicile vs. statutory residency vs. nonresident
- Allocate income by source and jurisdiction
- Identify credits, treaties, and reciprocity that prevent double taxation
- Surface compliance obligations — filings, reporting, withholding
- Recommend planning moves with a clear coordination plan with the client's tax professional
Output format
Residency and Domicile Analysis
For each jurisdiction at issue:
- Domicile: where is the client's "true, fixed, and permanent home"?
- Statutory residency: does the client meet the day-count or other tests in any state? (e.g., NY 183-day rule, CA "closest connections" test)
- Federal residency: Substantial Presence Test for foreign nationals
- Tie-breaker rules: under tax treaties for individuals dual-resident under domestic law
- Domicile-change considerations: what evidence supports change (driver's license, voter registration, property, time spent, family location, professional and social ties)
Income Sourcing
For each income type, determine which jurisdictions can tax it:
- Wages: typically sourced where work is performed; remote-work rules vary by state (convenience-of-employer rules in NY, NJ, AR, CT, DE, NE, PA)
- Self-employment / business income: sourced based on apportionment (sales, payroll, property) for multistate; permanent establishment for international
- Capital gains on securities: typically sourced to state of residence at sale; some states (e.g., CA) can claw back if accrued during residency
- Real estate gains: sourced to property location
- Rental income: sourced to property location
- Retirement income: federal source rules generally protect against state taxation by former state (Pension Source Tax Act)
- Stock options, RSUs: sourced to where work was performed during vesting period — multi-state grants are complex
- Foreign income: U.S. citizens taxed on worldwide income; foreign-earned income exclusion and foreign tax credit available
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.
- 23d ago First seen · 81 lines · 16 tokens per session scan A a82dfbe17c17
multi-jurisdiction-tax is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 16 tokens to every session and 1,227 once invoked, about $0.0001 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-24.
Other commands, from other repositories
financial-model
Build a financial model or business case with projections.
monitor
AML transaction monitoring and suspicious activity reporting.
refine
Refine vague legal queries into structured prompts through Socratic dialogue, with workflow recommendations and multi-lingual terminology guidance.
dd
A stock due-diligence checklist covering financial, commercial, legal, operational, and market checks. It marks each item as supported by available data, needing human review, or missing.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.