Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/gosuda/portal-tunnel/codebase-mapnpx skills add gosuda/portal-tunnel --skill codebase-mapgit clone --depth 1 https://github.com/gosuda/portal-tunnelWrote 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/codebase-map)<a href="https://agentmods.dev/skills/gosuda/portal-tunnel/codebase-map"><img src="https://agentmods.dev/badge/skills/gosuda/portal-tunnel/codebase-map.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 | $0.00045 | $0.00809 |
| Opus 5 | $0.00023 | $0.00404 |
| Sonnet 5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
codebase-map 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 4d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
portal-tunnel codebase map
Portal is a zero-knowledge tunneling relay + local runtime: exposes local HTTP/TCP/UDP services through self-hosted or public relays with end-to-end tenant TLS, ECH SNI hiding, MITM self-probe, multi-hop routing, and x402 payments.
Top-level packages
sdk/— client side. Tunnel exposure and relay API client, listener/session management, HTTP routing + proxying, MITM detection. Entry points:sdk/expose.go,sdk/listener.go,sdk/http.go,sdk/proxy.go,sdk/mitm.go. x402 route protection is applied here (sdk/http.go).portal/— relay side. API/server lifecycle (portal/api_server.go,portal/server.go), leases, proxying, identity, keyless TLS/ECH, overlay transports, policy, telemetry, ACME.portal/discovery/— relay gossip:announce.go(rate limiting),refresher.go(poll descriptors +POST /discovery/announceself-announce + peer refresh),relayset.go(validated pool, bans, route-planning state),relaystate.go,mols.go(route scoring).portal/x402/— payment gating:handler.go,payment.go,casper.go,x402.go, embedded browserclient.js. Facilitator mounts at/api/x402only whenX402_ENABLED.
types/— shared contracts: protocol/API/data models, identity & transport types, x402 types, and public path constants (types/paths.go).types/types.gounmarshals the embeddedconfig.toml/registry.json. Put shared constants and public path strings HERE.utils/— shared stateless helpers: API encoding, command dispatch (utils/cmd.go), files, paths, HTTP, name/network/TLS normalization, snapshots.cmd/— executables:cmd/portal-tunnel(client CLI),cmd/relay-server(relay + embedded SPA),cmd/portal-loadtest(make load-test), plus demo/payment apps.frontend/— React + Tailwind SPA (Vite). Built and embedded into the relay binary atcmd/relay-server/dist/app(//go:embed dist/*). Dev server athttp://localhost:5173; point at a live relay withVITE_PORTAL_API_BASE_URL.docs/— SvelteKit docs site (make build-docs, uses bun).extensions/vscode/— VS Code extension (start/stop tunnel commands, relay/host/name settings).
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.
- 4d ago First seen · 33 lines · 45 tokens per session scan A 54a12b403272
codebase-map is a skill published in the GitHub repository gosuda/portal-tunnel (265 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 809 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.
debugging-output-and-previewing-html-using-ray
Use when user says "send to Ray," "show in Ray," "debug in Ray," "log to Ray," "display in Ray," or wants to visualize data, debug output, or show diagrams in the Ray desktop application.
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/.
simplified-technical-english
Write user-facing and reviewer-facing technical text in ASD-STE100 Simplified Technical English style. Use when drafting PR descriptions, commit message bodies, UI copy, docs, error messages, procedures, onboarding text, or any product wording that must stay clear for non-native readers.
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…