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 instructions/xiaolai/mac-it-guy-pro/agents-mdgit 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.01786 | $0.01786 |
| Opus 5 | $0.00893 | $0.00893 |
| Sonnet 5 | $0.00357 | $0.00357 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade D, and why
mac-it-guy-pro AGENTS.md scanned grade D with 4 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- the remote-sudo ask stays on `hit`, because the sudo it looks for is inside Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
later commands as its own: `rm -rf /tmp/x && mkdir -p /tmp/x/bin` was denied Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`ssh host 'bash <(curl …)'` is real and prose containing a literal pipeline Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
fs=subprocess.run(['git','ls-files','-z'],capture_output=True,text=True).stdout.split('\0') How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working conventions for this repo
Shared by Claude, Codex, and any other agent working on mac-it-guy-pro.
Privacy discipline when testing against a real machine
This plugin's recipes can only be trusted if they are run, and running them means pointing diagnostic commands at a real person's Desktop, Downloads, Documents, network, and profile. That verification has caught real bugs and should continue. The output of it is the hazard, not the act.
Binding rules:
- Never print raw file names, paths, device names, addresses, or profile values from the operator's real directories. Print counts, aggregates, pass/fail, or field labels with values suppressed.
wc -linstead of the listing;grep -cinstead of the match; "OK (value suppressed)" instead of the value. - Never write a real person's name, employer, address, or file name into any tracked file — not into documentation, not into an example, and above all not into a test fixture. Use placeholders:
Ada,Zoë,example.com,MacBook Air M2. A placeholder tests exactly as well. - Prefer synthetic fixtures over the live machine. Build a temporary directory with the shape you need. Reach for the operator's real data only when the question is specifically "does this behave correctly against real-world mess," and then apply rule 1.
- Nothing personal in commit messages. They are the hardest place to scrub, because removing them rewrites published history.
- Redact before quoting. When a real value must be discussed to explain a finding, describe its shape ("a company name", "a 12-character prefix") rather than reproducing it.
Rule of thumb: this plugin instructs the IT guy to keep MAC addresses, private IPs, and device inventories out of the user's own profile. Hold the development process to the same standard it imposes on the product.
English only
All tracked content is English: documentation, prompts, skills, commands, code, comments, test fixtures, and commit messages. Values a user supplies at runtime may be in any language; nothing checked in may be.
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 · 119 lines · 1,786 tokens per session scan D b865d9383ca1
mac-it-guy-pro AGENTS.md is an instructions file published in the GitHub repository xiaolai/mac-it-guy-pro (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,786 tokens to every session, about $0.0089 per session on Opus 5. A static security scan graded it D with 4 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
app-it AGENTS.md
Instructions for Christian-Katzmann/app-it, covering agents.md, safe first command, verify — the one command, what this repo is and conventions that will surprise you.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
heimdall AGENTS.md
Instructions for randomittin/heimdall, covering working in the heimdall repo, the rules that actually block you, environment, conventions and heimdall — this repo is gated.
vmette CLAUDE.md
Instructions for chamuka-inc/vmette, covering vmette — project instructions, checks (run before considering work done), workspace layout, core library — crates/vmette/src/ and daemon — crates/vmette-daemon/src/.
ai-plugins AGENTS.md
Instructions for openEHR/ai-plugins, covering ai-plugins, repository purpose, structure, key conventions and development.
MPX68K CLAUDE.md
Claude Code instructions for YosAwed/MPX68K, covering claude.md, project overview, build commands, building the project and open in xcode (primary build method).