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 pjt222/agent-almanac --skill check-relocation-documentsgit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/check-relocation-documents)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/check-relocation-documents"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/check-relocation-documents/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/pjt222/agent-almanac/check-relocation-documents"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/check-relocation-documents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00094 | $0.03025 |
| Opus 5.5 | $0.00038 | $0.01210 |
| Sonnet 5.5 | $0.00019 | $0.00605 |
| Haiku 4.5 | $0.00009 | $0.00302 |
Grade A, and why
check-relocation-documents 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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check Relocation Documents
Verify that all required documents are present, valid, and properly prepared for each bureaucratic step of an EU/DACH relocation, generating an actionable list of missing items and translation needs.
When to Use
- After creating a relocation plan and before beginning bureaucratic procedures
- When preparing for a specific appointment (Buergeramt, Finanzamt, insurance office)
- When unsure which documents need certified translation or apostille
- After receiving a rejection or request for additional documents from an authority
- When a household member has a different nationality requiring separate document tracks
- As a periodic check during the relocation process to ensure nothing has been overlooked
Inputs
Required
- Relocation plan: Output from the plan-eu-relocation skill or equivalent, listing all bureaucratic steps
- Destination country: Germany, Austria, Switzerland, or other EU country
- Nationality/nationalities: For all household members
- Document inventory: List of documents currently in possession (originals and copies)
Optional
- Origin country: For determining which documents need apostille or Hague Convention legalization
- Employment contract: To determine employer-provided documents (e.g., Arbeitgeberbescheinigung)
- Language of existing documents: To identify translation needs
- Previous relocation experience: Prior EU registrations that may simplify requirements
- Special circumstances: Recognized refugees, EU Blue Card holders, posted workers (different document requirements)
Procedure
Step 1: List All Bureaucratic Steps
Extract every registration, application, and notification step from the relocation plan.
- Parse the relocation plan for all action items requiring document submission
- Categorize steps by authority type:
- Municipal registration offices (Buergeramt, Meldeamt, Einwohnerkontrolle)
- Tax authorities (Finanzamt)
- Health insurance providers (Krankenkasse, OeGK, Swiss insurer)
- Social security offices (Rentenversicherung, Sozialversicherung, AHV)
- Immigration/foreigners office (Auslaenderbehorde) if applicable
- Banks and financial institutions
- Schools and childcare facilities
- Vehicle registration (Kfz-Zulassungsstelle)
- Other (pet import, professional license recognition)
- Order steps according to the dependency chain from the relocation plan
- Note which steps share the same documents (to avoid redundant preparation)
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.
- 1mo ago First seen · 248 lines · 94 tokens per session scan A aa2a149c9491
check-relocation-documents is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed 5d ago), licensed MIT. It adds 94 tokens to every session and 3,025 once invoked, about $0.0004 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-03.
Other skills, from other repositories
crisis-holding
Draft crisis holding statements, journalist Q&A posture, and what-not-to-say guidance from confirmed incident facts, with a hard legal-counsel gate. Builds each statement through proven crisis-comms frameworks (holding-statement anatomy, SCCT, CAP order, the legitimate non-answer, bridge/flag/block).
cocoaudit
View and export the append-only session audit trail for regulated environments.
audit-add
Add a clearly marked manual CocoAudit event. Usage: $audit add " ".
audit-timeline
Render CocoAudit records as a compact chronological timeline. Usage: $audit timeline.
audit-ci
V2-native deterministic contract for the owning CocoPlus feature. Executes the behavior formerly delegated to audit-ci skill without registered runtime scripts.
audit-export
Export the full CocoAudit trail as a stakeholder-ready compliance document.