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 agentmods add skills/squadcodercom/squadcoder/il-invoice-organizernpx skills add squadcodercom/squadcoder --skill il-invoice-organizergit clone --depth 1 https://github.com/squadcodercom/squadcoderWhat 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 | $0.00198 | $0.03929 |
| Opus 5 | $0.00099 | $0.01965 |
| Sonnet 5 | $0.00040 | $0.00786 |
| Haiku 4.5 | $0.00020 | $0.00393 |
Grade A, and why
il-invoice-organizer 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 2d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IL Invoice Organizer
Instructions
Step 1: Identify Invoice Type and Source
Determine what documents the user has:
| Document Type | Hebrew | VAT Reclaimable | Categorization |
|---|---|---|---|
| Tax Invoice (300) | חשבונית מס | Yes - extract VAT | Full categorization |
| Tax Invoice/Receipt (305) | חשבונית מס/קבלה | Yes - extract VAT | Full categorization |
| Receipt only (320) | קבלה | No VAT to reclaim | Payment record only |
| Credit Invoice (310) | חשבונית זיכוי | Yes - negative VAT | Reverse original category |
| Proforma (330) | חשבונית פרופורמה | No - not a tax document | For reference only |
Key: Only tax invoices (300, 305) allow VAT input deduction (nikui mas tsumos).
Step 2: Extract Invoice Data
Parse the following fields from each invoice:
| Field | Hebrew | Where to Find | Validation |
|---|---|---|---|
| Supplier name | שם הספק | Header | Must match TIN |
| Supplier TIN | מספר עוסק | Header | 9 digits with check digit |
| Invoice number | מספר חשבונית | Header | Sequential |
| Date | תאריך | Header | DD/MM/YYYY format |
| Net amount | סכום לפני מע"מ | Line items sum | Before VAT |
| VAT amount | סכום מע"מ | VAT line | = Net * 0.18 |
| Total amount | סכום כולל | Bottom | = Net + VAT |
| Allocation number | מספר הקצאה | B2B invoices above SHAAM threshold | SHAAM allocation required |
SHAAM allocation threshold timeline (Israel Tax Authority, accelerated rollout):
| Period | Threshold (pre-VAT) |
|---|---|
| 2025 (full year) | NIS 20,000 |
| 1 Jan 2026 to 31 May 2026 | NIS 10,000 |
| From 1 Jun 2026 | NIS 5,000 (permanent floor) |
A B2B tax invoice above the threshold without a valid SHAAM allocation number (מספר הקצאה) is not eligible for VAT input deduction. Always check the threshold for the invoice issue date, not today's date.
Step 3: Extract VAT (1/6 Rule)
Israeli VAT is 18% (raised from 17% effective 1 January 2025). For invoices where only the total (gross) is visible:
What ships with it
5 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.
- 2d ago First seen · 219 lines · 198 tokens per session scan A 1d54fc9499f2
il-invoice-organizer is a skill published in the GitHub repository squadcodercom/squadcoder (11 stars, last pushed 2mo ago), licensed MIT. It adds 198 tokens to every session and 3,929 once invoked, about $0.0010 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-30.
Other skills, from other repositories
write-zot-themes
Help the user create, install, or package zot themes, including theme-only extensions.
python-testing
Python testing best practices using pytest including fixtures, parametrization, mocking, coverage analysis, async testing, and test organization. Use when writing or improving Python tests.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration. Use when setting up containerized development environments or reviewing Docker configurations.
python-patterns
Python-specific design patterns and best practices including protocols, dataclasses, context managers, decorators, async/await, type hints, and package organization. Use when working with Python code to apply Pythonic patterns.
st-full-workflow
Use when the user asks to run the complete end-to-end Strikethroo workflow for a work order in one shot in this repository — triggers include full workflow, end-to-end, plan and execute, do everything, run the whole strikethroo workflow. Do not use when the user wants only one stage (create a plan, generate tasks, or…