profile

A command for viewing or updating the IT specialist’s stored record about a Mac computer. The record contains machine details, visit history, and memory-health checks.

In plain words
What is it for?
Showing the machine profile, reviewing its health, updating remembered details, and checking recorded IT visits.
Why use it?
It makes the assistant’s remembered machine information inspectable and editable instead of hidden or assumed.

Command

Part of the mac-it-guy-pro plugin — 8 skills, 12 commands, 4 agents, 2 hooks shipped together

Install

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.

agentmods
npx agentmods add commands/xiaolai/mac-it-guy-pro/profile
Clone the repo
git clone --depth 1 https://github.com/xiaolai/mac-it-guy-pro

Or install mac-it-guy-pro, the plugin that ships this one along with the rest of its 8 skills, 12 commands, 4 agents, 2 hooks.

Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,497 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01497
Opus 5 $0.00011 $0.00749
Sonnet 5 $0.00004 $0.00299
Haiku 4.5 $0.00002 $0.00150

Measured 2d ago against content hash 26a0a587e979, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

profile 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.

commands/profile.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Profile — auditable memory

Read ${CLAUDE_PLUGIN_ROOT}/skills/machine-profile/SKILL.md first — schema and update rules are binding. If uname is not Darwin, say this version supports Mac only and stop. If ~/ITGuy/machine.md does not exist, say there is no profile yet and point to /mac-it-guy-pro:onboard — then stop.

Resolve the subcommand from $ARGUMENTS; empty means show.

show

Print ~/ITGuy/machine.md verbatim, then a three-line footer:

  • How to reach him: list both triggers — the Summon: value and, when an IT guy: name is set, the derived _<name> — noting that capitalisation is irrelevant to either.
  • Visits on record: count of lines in ~/ITGuy/visits.log, with the date of the first and the latest.
  • Memory health: run bash "${CLAUDE_PLUGIN_ROOT}/scripts/lint-profile.sh" and summarise it in one line — counts by severity, nothing more. If it reports any CRITICAL, say so first and offer review immediately; a stored secret is not a footnote.
  • "This file is the IT guy's entire memory of this machine. Edit it or delete any line — whatever it says is what I'll believe next visit. What I've stopped believing is in history.md."

review — the deep memory audit

Run the linter first — it does the mechanical half deterministically:

bash "${CLAUDE_PLUGIN_ROOT}/scripts/lint-profile.sh"

It emits SEVERITY|rule|location|message per finding (exit 0 clean, 1 findings, 2 no profile) and checks what prose cannot enforce: stored secrets, untagged facts, conclusions with no retest date or method, overdue retests, told-facts over a year old, stale measurements, an unverified or 60-day-old connection status, a summon word missing its underscore, the 120-line cap, malformed ledger lines, and demoted beliefs missing from history.md.

Act on CRITICAL findings before anything else and before showing the profile. A stored private IP, MAC address, UUID, share link, or password is a privacy failure, not a tidiness issue: remove it from machine.md and history.md, write a redacted ledger event that records the removal without repeating the value, and tell the user plainly what was stored and that it is gone.

Read the full file on GitHub · 67 lines

Changes

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.

  1. 2d ago First seen · 67 lines · 22 tokens per session scan A 26a0a587e979

Subscribe to this mod's changes

profile is a command published in the GitHub repository xiaolai/mac-it-guy-pro (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,497 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.