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 AlexTeplovCPA/it-contractors-skills --skill identifying-income-sourcesgit clone --depth 1 https://github.com/AlexTeplovCPA/it-contractors-skillsWrote 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/alexteplovcpa/it-contractors-skills/identifying-income-sources)<a href="https://agentmods.dev/skills/alexteplovcpa/it-contractors-skills/identifying-income-sources"><img src="https://agentmods.dev/badge/skills/alexteplovcpa/it-contractors-skills/identifying-income-sources/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/alexteplovcpa/it-contractors-skills/identifying-income-sources"><img src="https://agentmods.dev/badge/skills/alexteplovcpa/it-contractors-skills/identifying-income-sources.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.00109 | $0.01498 |
| Opus 5 | $0.00055 | $0.00749 |
| Sonnet 5 | $0.00022 | $0.00300 |
| Haiku 4.5 | $0.00011 | $0.00150 |
Grade A, and why
identifying-income-sources 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identifying Income Sources
Organize the user's income sources before deeper field mapping begins.
Core Rules
- Organize income sources before trying to finalize field amounts.
- Identify income by channel and support, not by vague tax concepts alone.
- Do not assume deposits are income unless the user confirms the source or support exists.
- Separate business income, slip-based income, reimbursements, and unclear receipts where possible.
- Preserve uncertainty when support is incomplete.
- Organize and flag, do not advise.
- Do not determine final filing positions.
- Do not conclude employment status, contractor status, or PSB status.
- Do not invent income totals.
- Do not assume all T4A amounts belong in T2125.
- Do not state that the user is ready to file.
- Use this phrase where relevant: "That is outside what this workflow covers. It is a question for a CPA before you file."
Inputs
Do not ask the user to share SIN, business number, account numbers, or client names. Use general descriptions and rounded amounts.
Accept any of:
- user explanation in chat
- uploaded slips such as T4A or T4
- invoice summaries
- platform summaries
- bookkeeping exports
- income summary spreadsheet
- bank deposit summaries
- payment processor summaries such as Stripe, Wise, PayPal, or Deel records
Minimum useful input:
- who paid the user
- how the user was paid
- whether any slips were received
- whether any platform or foreign income existed
Read from the shared input schema where available: case_id, tax_year, engagement_mode, user_profile, facts.business_activity, facts.income_channels, facts.slips_received, facts.foreign_income, documents.slips, documents.summaries, transactions.income_items, review_state.
Workflow
1. Establish the income context
Determine whether the user had:
- only self-employment income
- self-employment plus employment income
- self-employment plus slip-based contract income
- self-employment plus foreign or platform income
- reimbursements or other unclear receipts
- mixed sole proprietor and corporate activity if mentioned
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 · 184 lines · 109 tokens per session scan A c93de031e2bb
identifying-income-sources is a skill published in the GitHub repository AlexTeplovCPA/it-contractors-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 109 tokens to every session and 1,498 once invoked, about $0.0005 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
tax-calculator
Calculate tax implications of trades and generate tax reports.
jangbu-import
A data-import workflow for turning bank files, card records, spreadsheets, receipts, tax invoices, and statement PDFs into a standard set of 13 transaction fields. OCR, or optical character recognition, is used to read information from document images and PDFs.
jangbu-connect
A setup guide for connecting Korean tax, bank, card, and social-insurance data through CODEF, an external API service. It explains how users obtain their own CODEF credentials and store them locally.
jangbu-tax
A financial-reporting tool that summarizes categorized transactions into a profit-and-loss statement and a simplified balance sheet. A profit-and-loss statement covers income and expenses over a period; a balance sheet shows assets, liabilities, and equity at a date.
accountant-expert
Expert-level accounting, tax, financial reporting, and accounting systems. Use when the user mentions accounting, tax, financial reporting, GAAP, or IFRS, or when the task involves Accounting Principles, Financial Statements, Tax & Compliance, or Accounting Systems.
jaz-recipes
Use this skill when modeling complex multi-step accounting transactions — anything that spans multiple periods, involves changing amounts, or requires linked entries. Covers 16 IFRS-compliant recipes (prepaid amortization, deferred revenue, loans, IFRS 16 leases, hire purchase, fixed deposits, asset disposal, FX…