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 skills add melodic-software/claude-code-plugins --skill machine-profilegit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/skills/melodic-software/claude-code-plugins/machine-profile)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/machine-profile"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/machine-profile/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/machine-profile"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/machine-profile.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00083 | $0.02151 |
| Opus 5.5 | $0.00033 | $0.00860 |
| Sonnet 5.5 | $0.00017 | $0.00430 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
machine-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 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Record, once per machine, what the host has and which identity domains it holds, with the observation behind every value, so a plugin setup run starts from observed answers and a kept default says whether anyone looked. The profile drives setups; it never replaces their prerequisite logic. Design and rulings: machine-profile-design, placement in ADR 0041.
Everything here is read-only except two steps the operator confirms in that turn: record --confirm (writes the profile document) and apply --confirm (prints what to hand to each setup; it writes nothing itself).
Actions
<script> is bash "${CLAUDE_SKILL_DIR}/scripts/profile.sh". Every command that reads or writes the store takes --data-dir "${CLAUDE_PLUGIN_DATA}".
- profile (default). Run
/harness-ops:prerequisites, save its table to a scratch file, then run<script> discover --prerequisites <file>and print what it observed: machine facts, then each identity domain with its tree, git include,ghdirectory and verdicts. Offer to record it. On the operator's yes, run<script> record --data-dir ... --confirm <saved discover output>; without--confirmit validates and writes nothing. - diff.
<script> diff --data-dir ... --prerequisites <file>compares the stored document with fresh discovery. Empty output and exit 0 mean nothing changed: say so and ask nothing. Exit 4 lists each difference with both values and bothobserved_byentries. The store cannot tell a hand edit from a host change, so report the difference and do not attribute it. - explain
<key>.<script> explain --data-dir ... <key>prints the stored record and the command or path behind it. - apply
--option <key>. Rundifffirst and show it. Then<script> apply --data-dir ... --option <key>prints the plan. Only after the operator says yes in that turn, add--confirm. Setup skills aredisable-model-invocation: true, so ahandoffline is relayed for the operator to type as/<plugin>:setup; the model does not invoke it. An option recorded under a domain is a per-domain identity: the script reports aconflictand stops for it, and it is never put into the singlepluginConfigsslot.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · -17 tokens per session d8411d2627cb
- 3d ago Changed · +2 lines 11aeadb0720a
- 8d ago Changed 3685974418c8
- 13d ago Changed c451d5373ca6
- 14d ago First seen · 74 lines · 100 tokens per session scan A 16afcdd79ab2
machine-profile is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 2,151 once invoked, about $0.0003 per session on Opus 5.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-10-02.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
pass-function-as-arg
For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.