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/xiaolai/mac-it-guy-pro/networkgit clone --depth 1 https://github.com/xiaolai/mac-it-guy-proWhat 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.00028 | $0.01846 |
| Opus 5 | $0.00014 | $0.00923 |
| Sonnet 5 | $0.00006 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
network 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network — measure first, spend last
Read ${CLAUDE_PLUGIN_ROOT}/skills/home-network/SKILL.md first — the layer model, the fix ladder, and the boundaries are binding. Read ${CLAUDE_PLUGIN_ROOT}/skills/it-core/SKILL.md for the safety contract and ${CLAUDE_PLUGIN_ROOT}/skills/machine-profile/SKILL.md before writing anything to the profile. Read ~/ITGuy/machine.md if it exists. If uname is not Darwin, say this version supports Mac only and stop.
Confirm this is the user's own network before scanning anything — ask explicitly with AskUserQuestion, do not infer it from context. The question is whether this is their home network or one they administer. If it is a coffee shop, an office, a campus, or shared accommodation they do not control, do the parts that only inspect this Mac and decline the rest — see the boundaries in the skill. Ask once per run, before the first discovery command, and never in place of it.
Network data is sensitive. Device names, addresses, MAC addresses, and the SSID together describe a household. Follow the privacy rule in the skill: keep them out of ~/ITGuy/machine.md, redact them from anything saved or shared, and warn the user before they paste a network report into a support chat or a forum.
Resolve the subcommand from $ARGUMENTS; empty means check. If $ARGUMENTS is non-empty but matches none of the six, treat it as a problem description — name the six subcommands, say which one you think fits, and confirm before running it.
check — the health report
- Run the measurements in
${CLAUDE_PLUGIN_ROOT}/skills/home-network/references/diagnostics.md: Wi-Fi signal and SNR here,networkQualityidle, ping to the router and beyond, DNS in use, device count. - Report in the it-core report format, one row per area (Wi-Fi signal · Speed · Responsiveness · Router link · Internet link · Devices), each with its own 🟢/🟡/🔴 so a single bad area is visible rather than averaged away.
- Lead the top line with the layer, not the number: "Your Wi-Fi is the bottleneck, not your internet plan" is the sentence the user needs.
- End with exactly one recommended next step: read the profile's network notes and Watch List first to see which rungs have already been applied, then recommend the lowest rung of the fix ladder not yet tried. Without that check, a second visit repeats the advice of the first.
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 · 68 lines · 28 tokens per session scan A e769da1ebfec
network is a command published in the GitHub repository xiaolai/mac-it-guy-pro (5 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,846 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-31.
Other commands, from other repositories
type
Inject keystrokes via peekaboo type.
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
findmy
Look up Find My friend locations on macOS (name, location, staleness, distance) via Vision OCR of FindMy.app.
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
save
Save this conversation as a new or existing reusable context.
calendars
Manage macOS calendar events - list, search, create, update, delete with batch operations.