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/sfc-gh-eraigosa/dotfiles/ssh-keysgit clone --depth 1 https://github.com/sfc-gh-eraigosa/dotfilesWrote 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/commands/sfc-gh-eraigosa/dotfiles/ssh-keys)<a href="https://agentmods.dev/commands/sfc-gh-eraigosa/dotfiles/ssh-keys"><img src="https://agentmods.dev/badge/commands/sfc-gh-eraigosa/dotfiles/ssh-keys.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00316 |
| Opus 5 | $0.00008 | $0.00158 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
ssh-keys 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 5d 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.
What it actually says
Manage SSH keys across all hosts in ~/.ssh/config via the ssh-key-sync skill.
Arguments: $ARGUMENTS
Activate the ssh-key-sync skill. Parse $ARGUMENTS to determine intent:
list(or no args) — show the management table of all keys and their per-host authorization status:~/git/dotfiles/src/ssh-key-sync/ssh-key-sync.sh --listgenerate <name> [--no-sync]— create a new Ed25519 key. With--no-sync, keep it local only; otherwise distribute to every host in~/.ssh/config:~/git/dotfiles/src/ssh-key-sync/ssh-key-sync.sh [--no-sync] <name>delete <name1> [<name2> ...]— securely revoke and remove keys locally and from every remoteauthorized_keys:~/git/dotfiles/src/ssh-key-sync/ssh-key-sync.sh --delete <names...>
Always confirm with the user before delete or before distributing a new key — these are network-wide mutations. List operations are safe to run without confirmation.
After any mutating action, re-run --list and show the updated table so the user can verify.
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.
- 5d ago First seen · 23 lines · 15 tokens per session scan A 2bf836df0292
ssh-keys is a command published in the GitHub repository sfc-gh-eraigosa/dotfiles (46 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 316 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-30.
Other commands, from other repositories
config
Command "config" from 1shooperman/claude-env, covering claudenv config, usage, what it does, naming rules and errors.
activate
Command "activate" from 1shooperman/claude-env, covering claudenv <name>, usage, what it does, the default env and errors.
upgrade
Upgrade claudenv to a specific release or the latest version.
remove
Command "remove" from 1shooperman/claude-env, covering claudenv remove, usage, what it does and errors.
deactivate
Deactivate the current env and restore the original CLAUDECONFIGDIR.
list
Command "list" from 1shooperman/claude-env, covering claudenv list, usage and output.