Loading the registry…
Drive agterm, a native macOS terminal app, programmatically via its agtermctl CLI and a local control socket. Use when running inside an agterm session and asked to control the terminal: create, rename, close, select, or reorder sessions and workspaces; split panes; toggle the per-session scratch terminal; open or close overlay terminals and read their exit status; post a passive HUD message panel over a session while the user keeps typing; display the native fuzzy picker with caller-supplied choices and poll or cancel it; display an image inline via a bundled helper script; type into a session, copy its selection, or search its scrollback; post desktop notifications; manage windows (new, list, select, close, resize, move); change font size; or reload and edit the keymap and the agterm-scoped ghostty config. Also covers the window/workspace/session addressing model and the AGTERM_* environment a spawned shell sees, plus subscribe to status, notification, session lifecycle, and tree-change events; diagnose problems (keymap editor, custom actions, logs); and file a bug as a GitHub issue or a feature request / question as a GitHub Discussion.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- umputun/agterm
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- umputun/agterm ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
5 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
918 findings · 16.1s
v0.3.74
4 findings · 9.7s
v0.1.0
1 finding · 5.5s
v0.1.0
45 findings · 5.5s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 17, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 968 findings above stand exactly as their scanners reported them, at full severity.