testing-portal-tunnel-dashboard skillA
testing-portal-tunnel-dashboard is agent-read markdown (skill) from gosuda/portal-tunnel: How to drive the portal-tunnel agent dashboard bubbletea TUI end-to-end without a live agent or relay, using a stub control server plus a fabricated agent-endpoint.json..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Testing the portal-tunnel agent dashboard TUI standalone
The `portal-tunnel agent dashboard` TUI looks like it needs a running agent, but it only needs two things: a state dir containing `agent-endpoint.json`, and an HTTP server at the endpoint's `control_addr` that speaks the control API envelope.
## How the dashboard gets its data
- `portal-tunnel agent dashboard --state-dir DIR` reads `DIR/agent-endpoint.json` (`cmd/portal-tunnel/agent/control.go`, `endpointFilename = "agent-endpoint.json"`).
- The file is `{"control_addr":"HOST:PORT","token":"TOKEN"}`.
- Every poll tick it issues `GET http://<control_addr>/agent/status` with `Authorization: Bearer <token>` (`types.PathAgentStatus`).
- Responses must use the repo's API envelope: `{"ok": true, "data": <AgentStatusResponse>}`. Returning the raw status object without the envelope yields "Agent unavailable: api response is not ok" in the TUI.
- `AgentStatusResponse` / `AgentTunnelStatus` shapes live in `cmd/portal-tunnel/agent/api_types.go` (`tunnels[].metadata` is `types.LeaseMetadata`).
## Recipe
1. `go build -o /tmp/portal-tunnel ./cmd/portal-tunnel`
…Read the whole file at its exact version.
How to install
mdr add gosuda/portal-tunnel/testing-portal-tunnel-dashboard@git:20260922.927bd9emdr add gosuda/portal-tunnel/testing-portal-tunnel-dashboard@sha256:0df01bf3bbad857cPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ofqvmqngwy3djc3c)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260922.927bd9e latest | 2026-09-22 | 927bd9e | 4,952 B | A | view · diff |
| git:20260922.0810227 | 2026-09-22 | 0810227 | 4,897 B | A | view · diff |
| git:20260922.3a983e1 | 2026-09-22 | 3a983e1 | 4,406 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4952 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gosuda/portal-tunnel · 271 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ofqvmqngwy3djc3c GET https://markdownregistry.com/api/v1/resolve?ref=gosuda/portal-tunnel/testing-portal-tunnel-dashboard GET https://markdownregistry.com/api/v1/blob/0df01bf3bbad857ca5ec6119c12eaf4a6c6a3a872b7a192741c2d9ea2ace63a8
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.