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/yrebrac/stuart/profile-systemgit clone --depth 1 https://github.com/yrebrac/stuartWhat 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.00018 | $0.00411 |
| Opus 5 | $0.00009 | $0.00205 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
profile-system 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 yesterday.
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.
What it actually says
Read system-profile-rules.md in the linux-sysadmin skill directory, then handle the user's request.
With arguments
view (or no arguments)
- Read
${CLAUDE_PLUGIN_ROOT}/profiles/hardware.yaml,distro.yaml, andtoolchain.yaml - If profiles exist: present a concise summary table with key facts and profile ages
- If no profiles exist: tell the user and offer to run
refresh
refresh
- Re-gather all three profiles (hardware, distro, toolchain) following the skill's Gathering Strategy
- Archive any existing profiles first
- Report what was gathered and any changes from previous profiles
refresh hardware / refresh distro / refresh toolchain
- Re-gather only the specified profile
- Archive the existing file first
- Report what was gathered
audit
- Call
tool_info()on each active MCP server - Aggregate results — identify missing tools
- Present a table: server, tool, status, package, install command
- Write results to
toolchain.yaml
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.
- yesterday First seen · 45 lines · 18 tokens per session scan A 8526dd4630df
profile-system is a command published in the GitHub repository yrebrac/stuart (1 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 411 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
release
Merge PR, tag release, and create GitHub release with changelog notes using the release skill.
changelog
Generate a Keep a Changelog entry from git commits using the changelog skill.
pr
Commit changes, bump version, update changelog, and open a PR using the pr skill.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.