Skip to content
Back to skills

Verify

BSecurity

Build and drive a scratch podiomd daemon to verify changes at the real REST/WS surface without touching the user's live daemon or ~/.podiom.

  • 16 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 3, 2026
ai-agentsgobashapi

Works with

  • cli
  • api

Security analysis

B75/100
  • criticalSends environment variables or credentials to an external URL

Pro shows the line behind each finding and how to fix it

Scanned September 3, 2026

npx -y skills add Podiom/Podiom --skill verify --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify
[![Security: B — Skills Directory](https://www.skillsdirectory.com/api/skills/podiom-verify/badge)](https://www.skillsdirectory.com/skills/podiom-verify)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: verify
description: Build and drive a scratch podiomd daemon to verify changes at the real REST/WS surface without touching the user's live daemon or ~/.podiom.
---

# Verifying Podiom changes against a live daemon

The user's real daemon usually occupies 127.0.0.1:8787 — always run a scratch
daemon on another port with an isolated `PODIOM_HOME`.

## Build & launch

```bash
SCRATCH=$(mktemp -d)
go build -o $SCRATCH/podiomd ./cmd/podiomd     # embeds web/dist — run `cd web && npm run build` first if the SPA changed
mkdir -p $SCRATCH/home
PODIOM_HOME=$SCRATCH/home $SCRATCH/podiomd &   # first run scaffolds config.yaml + gateway.token, then FAILS on port 8787
```

First launch scaffolds `$SCRATCH/home/config.yaml` then dies on the port
conflict. Edit the scaffolded config's existing `server:` block (do NOT append
a second `server:` key — duplicate keys are a YAML parse error) to
`port: 18787`, then relaunch.

## Drive it

- Token: `TOKEN=$(cat $SCRATCH/home/gateway.token)`; every /api call needs
  `Authorization: Bearer $TOKEN`.
- REST: `curl -s -H "Authorization: Bearer $TOKEN" http://127.0.0.1:18787/api/...`
- Create an agent: `POST /api/agents {"name":"x","provider":"claude"}`;
  a session: `POST /api/sessions {"agent_name":"x","origin":"web"}`.
  Session creation composes instructions without running a turn — inspect
  `$SCRATCH/home/agents/<name>/workspace/CLAUDE.md` (or AGENTS.md for codex)
  to verify instruction-layer changes.
- WebSocket: dial `ws://127.0.0.1:18787/api/ws` with the bearer header. A
  tiny `go run` script using `nhooyr.io/websocket` (already in go.mod) works;
  send `{"type":...,"request_id":...}` JSON and read replies.
- SPA: fetch `/` and the hashed `/assets/index-*.js` to confirm new UI strings
  made it into the embedded bundle.

## Gotchas

- Don't drive turns with a real provider from a scratch daemon — the claude
  CLI uses the user's real login and burns their quota. Turn flows are covered
  by `internal/server/ws_test.go` patterns with `adapter.NewFake()`.
- Kill the scratch daemon when done; it starts schedulers and pollers.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.