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 mickpletcher/AI-Skills --skill container-homegit clone --depth 1 https://github.com/mickpletcher/AI-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/mickpletcher/ai-skills/container-home)<a href="https://agentmods.dev/skills/mickpletcher/ai-skills/container-home"><img src="https://agentmods.dev/badge/skills/mickpletcher/ai-skills/container-home/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/mickpletcher/ai-skills/container-home"><img src="https://agentmods.dev/badge/skills/mickpletcher/ai-skills/container-home.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.00057 | $0.01786 |
| Opus 5.5 | $0.00023 | $0.00714 |
| Sonnet 5.5 | $0.00011 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00179 |
Grade A, and why
container-home 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Home
Do Not Use When
- Do not use as a substitute for licensed engineering, permitting, electrical, structural, septic, or legal signoff.
- Required context is missing and cannot be reasonably inferred.
- A more specific skill in this repo is a better match.
Workflow
- Identify the exact task and available source material.
- Apply the domain rules and output format in this skill.
- State assumptions, uncertainty, and missing inputs clearly.
- Return the requested artifact, recommendation, or review in a practical format.
- Check the result against the validation checklist before finishing.
Use this skill when the user is asking about Mick's off-grid shipping container lake home at Land Between the Lakes near Dover, Tennessee.
Trigger When
- The user mentions the container home, lake home, container house, or container expansion
- The user mentions Stewart County, Dover TN, or LBL
- The task involves solar, septic permitting, water, off-grid systems, welding, fabrication, or layout decisions for this property
- The user wants project-aware Facebook post copy about the build
Intent
Provide project-specific context and guidance for the current build, the planned expansion, and the broader retirement-property strategy without making the user restate the full background every time.
Current Structure
- Two 40-foot high cube containers welded side by side
- Current living area is about 640 square feet
- The right wall and back wall are underground and reinforced with H-beams
- The structure is livable now and used as a weekend retreat
- Construction has been almost entirely owner-built and mostly solo
Systems
- Solar: 500W+ array, 4x105Ah battery bank, 2000W Renogy inverter, 12V distribution
- Planned solar upgrade: 15 kW for full-time residence use
- Water: own water supply on the property
- Waste: incinerator commode currently, no septic system yet
- Interior: framing, cedar finish, plumbing rough-in, propane refrigerator, and related work already underway
What ships with it
4 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.
- 1mo ago First seen · 184 lines · 57 tokens per session scan A c2ad438f45cb
container-home is a skill published in the GitHub repository mickpletcher/AI-Skills (20 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,786 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
bambu-labs
Dry-run, upload, and cautiously initiate local Bambu Lab print jobs from validated plain .gcode, using Bambu LAN FTPS/MQTT handoffs.
dfam-check
Measure mesh files against Design for Additive Manufacturing (DfAM) rules and report printability findings per process (FDM, SLS, SLA/DLP, metal PBF, MJF). Use when the user asks whether a part is printable, wants overhang/wall-thickness/support analysis of an .stl, .obj, .ply, or .3mf mesh, wants a build-orientation…
8051-mcu-debug
Use when debugging 8051-compatible microcontrollers, 51 MCU firmware, STC download issues, Keil C51 projects, interrupts, timers, UART, or startup failures.
cortex-m-debug
Use when debugging Cortex-M microcontrollers, firmware bring-up, SWD/JTAG sessions, faults, startup code, or flashing failures.
cortex-r5-debug
Use when debugging Cortex-R5 or Cortex-R firmware — TCM, MPU, caches, DFSR/DFAR aborts, exceptions, GIC/VIC interrupts, lockstep or split mode, ECC, or JTAG bring-up.
embedded-library-entry
Use when integrating, porting, configuring, or debugging third-party MCU embedded C libraries in bare-metal or RTOS projects.