dev-workflow

dev-workflow is a skill for Claude Code, Codex from gosuda/portal-tunnel. It costs 43 tokens per session (771 once invoked), scanned A, original, MIT.

A development checklist for the portal-tunnel project, which combines Go code with a frontend in one repository. It covers the commands used to format, check, build, lint, and test the project before committing.

In plain words
What is it for?
Use it when setting up the repository, installing tools, running Go and frontend checks, preparing a commit, or investigating pre-commit failures.
Why use it?
It keeps local checks aligned with the project’s continuous-integration checks and documents the required Go, Node.js, and development tools.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is make vet # go vet ./cmd/... ./portal/... ./sdk/... ./types/... ./utils/....

Install

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.

Made for: Claude Code, Codex.

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.

agentmods badge for dev-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/gosuda/portal-tunnel/dev-workflow.svg)](https://agentmods.dev/skills/gosuda/portal-tunnel/dev-workflow)
Your own site
<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>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 771 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 293e0974eaaa, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.agents/skills/dev-workflow/SKILL.md · 39 lines

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.4 via go.mod; the Makefile exports GOTOOLCHAIN=go1.26.4, so make targets self-pin even on other Go installs.
  • make install installs 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+.
  • bun is needed only for make 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 fmt runs gofmt -w . then goimports -w ., so goimports MUST be on PATH or the commit hook fails with goimports: No such file or directory — run make install first.
  • 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 buildbuild-tunnel + build-server (full artifacts).
  • make build-frontend builds the SPA (cd frontend && npm ci && npm run build) and copies frontend/dist/. into cmd/relay-server/dist/app (embedded by the relay via //go:embed dist/*).
  • make build-server-bin compiles only bin/relay-server; it assumes dist/app already exists (use after build-frontend, or the binary fails at startup asking you to run make build-frontend).
  • make build-tunnel cross-compiles cmd/portal-tunnel for linux/darwin/windows × amd64/arm64.
  • Shared Go build flags live in the Makefile var GO_BUILD_FLAGS (-trimpath -ldflags "-s -w"); the Dockerfile calls make build-server-bin rather than duplicating them.

Read the full file on GitHub · 39 lines

Changes

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.

  1. 6d ago First seen · 39 lines · 43 tokens per session scan A 293e0974eaaa

Subscribe to this mod's changes

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.

Related

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.

coollabsio/coolify · 62 tokens

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/.

superplanehq/superplane · 50 tokens

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/.

dograh-hq/dograh · 82 tokens

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.

n8n-io/n8n · 53 tokens

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…

Start9Labs/start-technologies · 129 tokens

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.

n8n-io/n8n · 70 tokens