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.
git clone --depth 1 https://github.com/izzzzzi/agent-asshWrote 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/rules/izzzzzi/agent-assh/assh)<a href="https://agentmods.dev/rules/izzzzzi/agent-assh/assh"><img src="https://agentmods.dev/badge/rules/izzzzzi/agent-assh/assh/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/rules/izzzzzi/agent-assh/assh"><img src="https://agentmods.dev/badge/rules/izzzzzi/agent-assh/assh.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.00560 | $0.00560 |
| Opus 5.5 | $0.00224 | $0.00224 |
| Sonnet 5.5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
assh 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 1mo 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
assh — SSH Workflow for LLM Agents
Use assh for SSH work so large remote output stays out of the agent context.
Install when missing:
npm i -g agent-assh
assh version
Agent Algorithm
Need SSH?
├── Have a key file? → assh connect -H HOST -u USER -i KEY -n NAME
├── Have SSH config alias? → assh connect --ssh-config ALIAS -n NAME
├── Pasted provider block? → save to 0600 temp → assh connect-info --file TMP -n NAME → rm
├── First-contact w/ pass? → assh connect -H HOST -u USER -E PASS_ENV -n NAME
└── Picky gateway? → assh connect ... --force-pty -n NAME
Quick Reference
| Command | What |
|---|---|
assh session exec -s SID -- "cmd" |
Run command in tmux session |
assh session read -s SID --seq N --limit 50 |
Read paginated output |
assh session close -s SID |
Close session |
assh exec -H HOST -u USER -- "cmd" |
One-off command, no tmux |
assh read --id ID --raw |
Read stored exec output |
assh transfer put/get/read/list/stat/mkdir/rm/mv/sync |
File operations |
assh session service -s SID --action restart --service NAME |
Service mgmt |
assh session exec -s SID -- "docker ps" |
Docker/db/anything else — via exec |
assh session exec-async -s SID -- "cmd" |
Background job |
assh fleet exec -H H1 -H H2 -u root -- "cmd" |
Multi-host |
assh scan -H HOST -u USER |
Host inventory JSON |
assh transfer read -H HOST -u USER --path FILE |
Read remote file |
Security Rules
- Passwords only through env vars. No
--passwordflag. [REDACTED:type]+"redacted":true= command succeeded, do not retrydangerous_command_requires_confirmation→ ask user before--confirm-danger- Never put passwords in arguments. Never echo passwords.
See skills/assh/ for detailed references.
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.
- 1mo ago First seen · 53 lines · 560 tokens per session scan A f12465f4f3bd
assh is a cursor rule published in the GitHub repository izzzzzi/agent-assh (21 stars, last pushed 2mo ago), licensed MIT. It adds 560 tokens to every session, about $0.0022 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-08-30.
Other cursor rules, from other repositories
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
hatch3r-operability
Operability patterns in user code — liveness / readiness / startup probes, graceful shutdown, feature flags, runbook URL annotations, health endpoints.
hatch3r-scalability
CQ6 Scalability Quality measurement rule — stateless-handler ratio, back-pressure pattern adoption, idempotency-key adoption on POST/PUT/PATCH, queue offloading for >1s ops, pool sizing per concurrency profile.
hatch3r-progressive-delivery
Progressive delivery — canary, blue-green, feature-flag rollout with auto-rollback on SLO burn; staged rollout to prevent CrowdStrike-class incidents.
hatch3r-observability-metrics
Metrics, SLO/SLI definitions, alerting, and dashboard conventions for the project.
cloudflare-tunnel-routes
Persistent HTTPS URL for local Gradio/Streamlit/FastAPI/webhook services without deploying. Use when the user wants a stable permanent URL on a domain they own (not a throwaway URL, not managed hosting).