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 agents/zyqzyq/unfour/open_issuesgit clone --depth 1 https://github.com/zyqzyq/UnfourWhat 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.00864 |
| Opus 5 | $0.00000 | $0.00432 |
| Sonnet 5 | $0.00000 | $0.00173 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
OPEN_ISSUES 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Issues
Last scanned: 2026-06-29 (SSH vi/xterm request-mode verification pass).
P0 — Blocks core usage
None.
P1 — High priority
SSH Transport
- Encrypted key passphrase (Observed): The ssh-key crate 0.7.0-rc.10 has limited support for decrypting encrypted OpenSSH keys. Keys without passphrases work. Encrypted key loading returns a clear error guiding users to save a passphrase credential. Passphrase is read from SecretStore, never stored in SQLite.
- Real SSH release gate (Observed, release blocker): Password login, private-key login, PTY I/O, resize, search, history restore, TOFU first trust, mismatch rejection, fingerprint reset, keepalive, and reconnect remain
NOT VERIFIEDagainst a reachable live SSH server. This is the sole blocker for early basic release. Automated coverage passes.
P2 — Medium priority
- Host-key UI enhancement (Observed): View/reset fingerprint implemented. Trust confirmation dialog (first trust + mismatch) implemented. known_hosts import/export implemented. Fingerprint change confirmation without full reset is a future enhancement.
- Lint warning cleanup (Observed): 53 warnings across
packages/api-client,packages/database,packages/ssh-terminal,packages/ui, andapps/desktop. Predominantlyreact-hooks/refsfalse positives from TanStack Query destructuring. Reduced from 64 in commit3649a2dvia pure-function extraction anduseEffectsync-pattern refactoring. No errors; none block builds. - xterm 6 request-mode workaround (Observed):
@xterm/[email protected]throwsReferenceError: i is not definedin itsrequestModeparser when vi emitsCSI ... $p/CSI ? ... $pmode-query sequences during full-screen startup. The SSH transport and vi process remain live, but xterm rendering can stop.packages/ssh-terminalfilters those request-mode sequences beforeterminal.write; live vi verification on 2026-06-29 confirmedfiltered xterm request-mode sequenceis observed, the xterm error is not reproduced, and vi insert/edit/exit interaction works. Version evaluation on 2026-06-29 vianpm viewfound@xterm/xtermcurrent stable remains6.0.0;6.1.0is beta-only, while@xterm/[email protected]and@xterm/[email protected]are current stable. Do not upgrade/downgrade in this batch; revisit when xterm 6.1 has a stable release or in a dedicated beta/downgrade compatibility test.
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.
- 2d ago First seen · 39 lines · 0 tokens per session scan A b0c9db866037
OPEN_ISSUES is an agent published in the GitHub repository zyqzyq/Unfour (2 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 864 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.
Other agents, from other repositories
altai-implementer
Implements one bounded ALTAI roadmap slice and its tests. Default working agent for roadmap PRs.
altai-test-triage
Triages failing tests/logs into product defects, flaky tests, environment problems, and pre-existing failures.
altai-explorer
Read-only ALTAI repository exploration. Use when file ownership or existing patterns are unclear before implementing a roadmap item.
altai-reviewer
Read-only diff review for a risky ALTAI PR. Reports actionable findings only.
Test Engineer
Writes tests first, then implementation. Strict TDD.
researcher
Sample subagent that does focused research on a single question.