A checklist and work plan for preparing an SSH application for an early release. SSH is a protocol used to connect securely to remote computers, and the plan covers testing that connection and its terminal features against a reachable server.

Use it to manually verify password and private-key login, encrypted key storage, terminal input and output, resizing, search, history restoration, host-key mismatch warnings, fingerprint reset, keepalive, and reconnect behavior.

It identifies the live checks still needed before release, including different login methods, host-key trust, reconnect behavior, and terminal state. It also sets boundaries against changing core code unless testing confirms a blocker.

NEXT_STEPS — Agent for coding agents by zyqzyq: A checklist and work plan for preparing an SSH…

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 agents/zyqzyq/unfour/next_steps

Clone the repo

git clone --depth 1 https://github.com/zyqzyq/Unfour

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/zyqzyq/unfour/next_steps.svg)](https://agentmods.dev/agents/zyqzyq/unfour/next_steps)

Your own site

<a href="https://agentmods.dev/agents/zyqzyq/unfour/next_steps"><img src="https://agentmods.dev/badge/agents/zyqzyq/unfour/next_steps.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,107 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.02107
Opus 5	$0.00000	$0.01053
Sonnet 5	$0.00000	$0.00421
Haiku 4.5	$0.00000	$0.00211

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

Security

Grade A, and why

NEXT_STEPS 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 3d 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.

docs/archive/agents/NEXT_STEPS.md · 85 lines

How it starts

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

Next Steps

Last scanned: 2026-06-14 (release readiness smoke verification pass).

Recommended: Release Gate and Preparation

Priority order:

Live SSH release gate verification
- Goal: Verify the complete SSH user journey against a reachable live SSH server to unblock early basic release.
- Scope:
  - password login
  - private-key login (unencrypted + passphrase-encrypted via SecretStore)
  - PTY input/output
  - resize
  - search
  - terminal history restore (hydration on app reopen)
  - TOFU first trust (host-key fingerprint recording)
  - mismatch rejection (fingerprint change detection and warning)
  - fingerprint reset
  - keepalive / reconnect (unexpected disconnect recovery)
- Forbidden: Do not modify SSH engine, terminal package, or SecretStore code unless a confirmed blocker is found during verification.
- Risk: May reveal timing, race condition, or platform-specific issues not covered by automated tests.
- Prerequisites: A reachable SSH server with both password and key authentication configured. The server must be accessible from the test machine running the Unfour desktop app.
- Acceptance criteria: Every item in the scope list above is manually verified against the live server and recorded as PASS or FAIL.
- Independent commit: No code change expected; fix only confirmed blockers.
- Evidence: OPEN_ISSUES.md P1 — "Real SSH release gate" (release blocker); PROJECT_STATE.md Known Limitations — "Release gate — live SSH verification"
- Recommended model: If code fixes are needed, use Codex / stronger coding model (Rust async, russh, cross-layer event streaming). If verification only, human or weaker cheaper model is sufficient.
macOS and Linux release smoke
- Goal: Verify app startup and real OS keychain create/read/delete on both remaining desktop targets.
- Scope: App launch, window rendering, SecretStore credential create/read/delete for SSH passwords, SSH key passphrases, PostgreSQL passwords, and MySQL passwords.
- Forbidden: Do not change Cargo.toml keyring feature flags or SecretStore crate code unless a confirmed blocker is found.
- Risk: Platform-specific keyring API differences may surface runtime errors.
- Prerequisites: Access to macOS and Linux machines or CI runners with keychain/keyring services.
- Acceptance criteria: No startup crash or blank screen; Apple Keychain and Linux Secret Service pass all four credential categories.
- Independent commit: No code change expected; fix only confirmed blockers.
- Evidence: OPEN_ISSUES.md Environment — "macOS/Linux startup and keychain"; PROJECT_STATE.md Known Limitations — macOS/Linux release smoke
- Recommended model: Codex / stronger coding model (only if code fixes are needed)

Read the full file on GitHub · 85 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.

3d ago First seen · 85 lines · 0 tokens per session scan A a5fbdd52639b

Subscribe to this mod's changes

NEXT_STEPS is an agent published in the GitHub repository zyqzyq/Unfour (2 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,107 tokens. 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.

Git and workflow Planning Releases api-client local-first mcp ssh tauri

NEXT_STEPS

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Next Steps

Recommended: Release Gate and Preparation

What this file has done since we first saw it

Other agents, from other repositories

deploy-agent

release

altai-implementer

altai-explorer

altai-reviewer

altai-test-triage