applications

A Seenode application management tool for web apps, background workers, and private internal services. It covers app details, packages, build settings, scaling, and deployments.

In plain words
What is it for?
Use it to list or inspect Seenode apps, check build and start commands, change packages or scaling, configure automatic deployment, restart or duplicate apps, and trigger deployments.
Why use it?
It avoids switching between deployment settings and app controls when you need to inspect or change how a Seenode app runs. It also makes redeploying, restarting, or duplicating an app more direct.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/seenode/seenode-agent-plugin/applications
Any agent
npx skills add seenode/seenode-agent-plugin --skill applications
Clone the repo
git clone --depth 1 https://github.com/seenode/seenode-agent-plugin

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 923 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 $0.00063 $0.00923
Opus 5 $0.00032 $0.00462
Sonnet 5 $0.00013 $0.00185
Haiku 4.5 $0.00006 $0.00092

Measured yesterday against content hash 377362d6407e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

applications 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 yesterday.

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.

skills/applications/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage Seenode applications

Types

Type Public URL Custom domains Port
web Yes (*.seenode.app) Yes Required
worker No No Usually omit
private No (internal only) No Required

list_applications filters by type and defaults to web. Call again with worker / private when needed — there is no all-types list.

Discovery

get_current_team()
list_applications(application_type="web", project_id=null, page=1)
get_application(application_id=...)
get_build_settings(application_id=...)
get_deployments(application_id=...)
list_images(image_type="application")
list_application_packages()
list_storage_packages()

Always get_application / get_build_settings before mutating so omitted fields can be carried forward.

Update metadata / package / scale

update_application(
  application_id=...,
  custom_name=null,
  description=null,
  project_id=null,
  package_id=null,    # paid tier from list_application_packages — needs credit approval
  scale=null,         # 1–10 instance multiplier; must be 1 when storage is attached
  auto_deploy=null    # deploy-on-push toggle
)

Build/run commands, runtime image, port, root directory, and git branch are not here — use update_build_settings. Package ≠ runtime.

Update build settings (redeploys)

update_build_settings(
  application_id=...,
  build_command=null,
  run_command=null,
  image_id=null,        # from list_images
  root_directory=null,
  port=null,
  git_branch=null
)

Side effect: starts a new build/deployment immediately. Prefer wait_for_deployment afterwards; use get_application_logs on failure.

Runtime changes mean changing image_id / creating with runtime — never via env vars named RUNTIME.

Restart (no rebuild)

restart_application(application_id=...)

Restarts running instances without rebuilding from git. Requires at least one prior successful deployment. Env-var changes already trigger a similar restart.

Read the full file on GitHub · 114 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. yesterday First seen · 114 lines · 63 tokens per session scan A 377362d6407e

Subscribe to this mod's changes

applications is a skill published in the GitHub repository seenode/seenode-agent-plugin (2 stars, last pushed 23d ago), licensed MIT. It adds 63 tokens to every session and 923 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens