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 commands/omarshahine/homeclaw/uploadgit clone --depth 1 https://github.com/omarshahine/HomeClawWrote 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/commands/omarshahine/homeclaw/upload)<a href="https://agentmods.dev/commands/omarshahine/homeclaw/upload"><img src="https://agentmods.dev/badge/commands/omarshahine/homeclaw/upload.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01286 |
| Opus 5 | $0.00008 | $0.00643 |
| Sonnet 5 | $0.00003 | $0.00257 |
| Haiku 4.5 | $0.00002 | $0.00129 |
Grade A, and why
upload 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 3d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the full TestFlight loop for HomeClaw via fastlane: generate notes, archive, upload to App Store Connect, submit to the External Testers group, tag the release, and confirm processing. The pipeline is long (8–20 min) so it MUST be run via Monitor so progress events stream into the conversation as they happen.
Pre-flight
-
Verify the working tree is clean and on
main:git status git rev-parse --abbrev-ref HEADAbort if dirty or on a feature branch — release builds should ship from
main. -
Check what's shipping. Generate release notes from commits since the last release tag (release tags are
v{version}+{build}; the Fastfile auto-strips the+buildsuffix when re-archiving so a stale tag won't break it):LAST_TAG=$(git describe --tags --abbrev=0 --match 'v*' 2>/dev/null) git log --oneline "$LAST_TAG..HEAD" -
Draft tester notes to a file (NOT inline — multiline + bullet points read better, and the file persists if you need to retry the submit step). Keep it user-facing: what features they get, what bugs were fixed. Avoid commit-hash speak.
# Write notes to /tmp/homeclaw_testflight_notes.txt
Run the pipeline (with Monitor)
The beta lane does: prepare (xcodegen + MCP build) → archive → export → upload → submit external. It exits non-zero on any failure. Use run_in_background so the Monitor can stream from its log file while you keep working.
fastlane beta notes_file:/tmp/homeclaw_testflight_notes.txt 2>&1 | tee /tmp/homeclaw_archive.log
Run with run_in_background: true. Then arm a Monitor to surface milestones:
tail -f /tmp/homeclaw_archive.log | grep -E --line-buffered "✓|finished successfully|Error|error|fail|FAIL|Submitting|Uploading|Build [0-9]+|TestFlight|version|warning|Traceback|EXPORT SUCCEEDED|Upload succeeded|external group"
The grep alternation MUST cover failure signatures (Error|fail|Traceback) — silence is not success.
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.
- 3d ago First seen · 92 lines · 16 tokens per session scan A 53f3d759bcd6
upload is a command published in the GitHub repository omarshahine/HomeClaw (164 stars, last pushed 10d ago), licensed MIT. It adds 16 tokens to every session and 1,286 once invoked, about $0.0001 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 commands, from other repositories
capture
Capture live screens/windows or ingest video; adaptive frames + contact sheet.
click
Target UI elements via peekaboo click.
type
Inject keystrokes via peekaboo type.
paste
Paste text or rich content via peekaboo paste.
clean
Prune snapshot caches via peekaboo clean.
drag
Execute drag-and-drop flows via peekaboo drag.