Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/gosuda/portal-tunnel/dev-workflow)<a href="https://agentmods.dev/skills/gosuda/portal-tunnel/dev-workflow"><img src="https://agentmods.dev/badge/skills/gosuda/portal-tunnel/dev-workflow.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.00043 | $0.00771 |
| Opus 5 | $0.00022 | $0.00385 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
dev-workflow 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 6d 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.
portal-tunnel dev workflow
Toolchain
- Go pinned to
go1.26.4viago.mod; the Makefile exportsGOTOOLCHAIN=go1.26.4, somaketargets self-pin even on other Go installs. make installinstalls the pinned dev tools:[email protected]and[email protected](into$(go env GOPATH)/bin, usually~/go/bin— put it on PATH).- Frontend build/test needs Node 22+.
bunis needed only formake build-docs.
Verification (CI commands, from AGENTS.md)
Run these three before pushing; they are what CI enforces:
make vet # go vet ./cmd/... ./portal/... ./sdk/... ./types/... ./utils/...
make lint # golangci-lint run (same package set)
make test # go test -coverprofile=coverage.out (same set) + `cd frontend && npm test` (vitest)
Per AGENTS.md, run tests only when needed/asked; make tidy is local maintenance, not a CI gate.
Pre-commit hooks
.pre-commit-config.yaml runs whitespace/EOL/BOM fixers, golangci-lint (config-verify, --new-from-rev HEAD --fix, and full --fix), plus local make fmt and go vet ./....
make fmtrunsgofmt -w .thengoimports -w ., sogoimportsMUST be on PATH or the commit hook fails withgoimports: No such file or directory— runmake installfirst.- Note the golangci-lint version differs between pre-commit (
v2.10.1) and the Makefile (v2.11.1); expect minor lint-behavior drift.
Build
make build→build-tunnel+build-server(full artifacts).make build-frontendbuilds the SPA (cd frontend && npm ci && npm run build) and copiesfrontend/dist/.intocmd/relay-server/dist/app(embedded by the relay via//go:embed dist/*).make build-server-bincompiles onlybin/relay-server; it assumesdist/appalready exists (use afterbuild-frontend, or the binary fails at startup asking you to runmake build-frontend).make build-tunnelcross-compilescmd/portal-tunnelfor linux/darwin/windows × amd64/arm64.- Shared Go build flags live in the Makefile var
GO_BUILD_FLAGS(-trimpath -ldflags "-s -w"); the Dockerfile callsmake build-server-binrather than duplicating them.
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.
- 6d ago First seen · 39 lines · 43 tokens per session scan A 293e0974eaaa
dev-workflow is a skill published in the GitHub repository gosuda/portal-tunnel (266 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 771 once invoked, about $0.0002 per session on Opus 5. 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-30.
Other skills, from other repositories
laravel-actions
Build, refactor, and troubleshoot Laravel Actions using lorisleiva/laravel-actions. Use when implementing reusable action classes (object/controller/job/listener/command), converting service classes/controllers/jobs into actions, orchestrating workflows via faked actions, or debugging action entrypoints and wiring.
superplane-changelog
When generating a SuperPlane changelog from merged commits. Use for "what's new" summaries with new integrations, new components/triggers, improvements, security updates, and bug fixes. Output is user-focused markdown in tmp/.
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
start9-frontend
Start9 house style for every Angular + Taiga UI web frontend (StartOS ui/setup-wizard, StartWRT, StartTunnel, brochure-marketplace, start9-store, ops-server, support-server). Use BEFORE writing or reviewing any frontend code in these apps — components, templates, styles/CSS, forms, dialogs/toasts, routing, state, DI…
n8n:human-like-code-review
Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.