Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/deciqAI/knowledge-skillsnpx agentmods add skills/deciqai/knowledge-skills/customs-reasonable-care-isf-checklistWrote 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/deciqai/knowledge-skills/customs-reasonable-care-isf-checklist)<a href="https://agentmods.dev/skills/deciqai/knowledge-skills/customs-reasonable-care-isf-checklist"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/customs-reasonable-care-isf-checklist/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/deciqai/knowledge-skills/customs-reasonable-care-isf-checklist"><img src="https://agentmods.dev/badge/skills/deciqai/knowledge-skills/customs-reasonable-care-isf-checklist.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.00086 | $0.00788 |
| Opus 5 | $0.00043 | $0.00394 |
| Sonnet 5 | $0.00017 | $0.00158 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
customs-reasonable-care-isf-checklist 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customs — Reasonable Care & ISF Compliance Checklist
Industry front door for checklist. Adds domain triggers, example, packs only. Parent Process unchanged. Not legal advice. Verify against current 19 CFR and CBP guidance.
Activate when: filing an entry or ISF; onboarding an importer (POA); building the compliance file; "did we file ISF in time?", "is our reasonable-care record complete?" Do NOT activate when: the shipment is exempt and no entry/ISF is required.
Why this variant
The parent checklist is a verifiable gate. Customs entry is a reasonable-care obligation with hard filing clocks (ISF) and 5-year recordkeeping. This maps those duties onto the parent's gate.
Domain inputs → parent's gate
- ISF (10+2): importer security filing transmitted no later than 24 hours before lading (ocean); update as info changes.
- Entry data: classification, valuation, origin, quantity — each supported and documented (reasonable care).
- POA: valid power of attorney + importer identity (KYC) on file.
- PGA: any FDA/USDA/EPA/other agency data flagged and filed.
- Recordkeeping: entry records retained 5 years from date of entry.
Worked example
New importer, ocean shipment, mixed goods, one FDA-regulated item. → Gate: ISF must transmit ≥24h pre-lading (late = liquidated damages up to $5k/violation); the FDA item needs prior notice + PGA data; POA + reasonable-care file must exist before entry. Any gap = do not file until cleared.
Compliance anchors
- 19 CFR 149 (ISF); 19 U.S.C. 1484/1485 reasonable care; 19 CFR 163 recordkeeping (5 yrs); PGA requirements.
Packs
- Solo broker: per-importer compliance folder template.
- Brokerage: ISF timing alerts into the deadline engine; PGA triage.
Red flags
- ISF filed inside the 24-hour window.
- Valuation/classification with no supporting record.
- PGA-regulated goods entered without agency data.
Verification
- ISF transmitted ≥24h before lading; updated on change
- Entry data supported & documented (reasonable care)
- Valid POA + importer KYC on file
- PGA requirements identified and met
- 5-year recordkeeping started
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 · 55 lines · 86 tokens per session scan A 542baacf6b8e
customs-reasonable-care-isf-checklist is a skill published in the GitHub repository deciqAI/knowledge-skills (10 stars, last pushed 10d ago), licensed MIT. It adds 86 tokens to every session and 788 once invoked, about $0.0004 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
compliance-check
Compliance pre-flight for a feature, campaign, or initiative — maps the data and activity involved, checks applicable regimes (privacy/GDPR-style, consumer protection, marketing rules, sector-specific), lists required approvals and notices, builds a gap list with remediation owners, and ends in a go/no-go…
legal-risk-assessment
Severity-by-likelihood legal risk register for a situation or deal — enumerates concrete risks, scores each one impact 1-5 × likelihood 1-5, renders a heat-map table, attaches mitigations to every risk at or above threshold, defines escalation criteria for immediate human counsel, and sets monitoring triggers. Use…
review-contract
Clause-by-clause contract review — inventories key clauses (term, termination, liability cap, indemnity, IP, payment, confidentiality, governing law, auto-renewal), flags deviations from market-standard positions with RED/YELLOW/GREEN severity and verbatim quotes, drafts redline language, and sets negotiation…
signature-request
Pre-signature gate and routing plan for a finalized document — verifies exact legal entity names, signatory authority, attached exhibits, filled blanks, consistent dates, and counterparty details, then sets the signing order (sequential vs. parallel, with reasons), writes envelope instructions for any e-sign tool, and…
prompt-master
Generates optimized prompts for AI tools. Activates only when the user explicitly asks to write, fix, improve, or adapt a prompt for a specific AI tool (LLM, Cursor, Midjourney, image AI, video AI, coding agents, etc.). Does not activate for general conversation, coding tasks, document writing, or other…
klauselinhalt-und-verbote-pruefen
Prüft eine AGB-Klausel anhand von Kontrollfähigkeit, gesetzlichen Klauselverboten und Interessenabwägung. Für B2C und B2B; liefert ein Klauselvotum mit Leitbild, Gegenposition und konkreter Rechtsfolge.