handle-startup-state

handle-startup-state is a skill for Claude Code from cognitedata/builder-skills. It costs 94 tokens per session (2,013 once invoked), scanned A, original, Apache-2.0.

A skill for restoring startup state in a Flows app. Startup state is an opaque value passed when the app opens, such as a deep-link URL, shared view, or host-provided argument.

In plain words
What is it for?
Use it to read initialState from the Cognite app connection and restore state before the first render.
Why use it?
It lets the app reopen the intended view instead of always starting with default state.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to read initialState from the Cognite app connection and restore state before the first render.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cognitedata/builder-skills/handle-startup-state
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.

Any agent
npx skills add cognitedata/builder-skills --skill handle-startup-state
Clone the repo
git clone --depth 1 https://github.com/cognitedata/builder-skills

Made for: Claude Code.

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 handle-startup-state

README.md
[![agentmods](https://agentmods.dev/badge/skills/cognitedata/builder-skills/handle-startup-state/github.svg)](https://agentmods.dev/skills/cognitedata/builder-skills/handle-startup-state)
Your own site
<a href="https://agentmods.dev/skills/cognitedata/builder-skills/handle-startup-state"><img src="https://agentmods.dev/badge/skills/cognitedata/builder-skills/handle-startup-state/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for handle-startup-state

Your own site · 80×15
<a href="https://agentmods.dev/skills/cognitedata/builder-skills/handle-startup-state"><img src="https://agentmods.dev/badge/skills/cognitedata/builder-skills/handle-startup-state.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 94 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00094 $0.02013
Opus 5.5 $0.00038 $0.00805
Sonnet 5.5 $0.00019 $0.00403
Haiku 4.5 $0.00009 $0.00201

Measured 2mo ago against content hash ff9d68070eb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

handle-startup-state 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 2mo 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.

skills/handle-startup-state/SKILL.md · 230 lines

How it starts

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

Handle Startup State

Reads the optional initialState string returned by connectToHostApp() and restores it before first render, so the app opens directly into the right view instead of always starting from defaults.

Requires @cognite/app-sdk's connectToHostApp() handshake already wired up. If auth isn't wired up yet, run the setup-flows-auth skill first.

What initialState actually is

initialState is a single opaque string, present on the object returned by connectToHostApp():

const { api, initialState } = await connectToHostApp();

Your app never needs to know how it got there — treat it the same way regardless of source:

  • A user opened a shareable URL your app previously wrote via api.syncInternalState(...) (the customAppInternalState URL param).
  • A host embedded your app with a startup argument baked in (a Flows dashboard widget, or any other surface that programmatically launches your app with initial arguments).
  • The app was reloaded and the current URL still has the param from an earlier syncInternalState call.

All three arrive through the same field. Design your restore logic once and it covers all of them.

Step 1 — Decide your encoding

Pick one encoding and use it consistently:

  • Serialized route (a path string) — if your app's state maps cleanly onto a URL you'd otherwise navigate to.
  • JSON string — if you need multiple independent fields (active tab, filters, selected IDs). This is the more common choice and the one used below.

Step 2 — Read initialState on mount, defensively

Restore before the first meaningful render. Malformed state must never crash the app — the host cannot guarantee the string is well-formed (it never parses it either), and an older app version may have written a different shape.

import { useEffect, useRef, useState } from 'react';
import { connectToHostApp, type HostAppAPI } from '@cognite/app-sdk';

interface AppState {
  activeTab: string;
  selectedAssetId?: string;
  filters: { status: string };
}

const DEFAULT_STATE: AppState = {
  activeTab: 'overview',
  filters: { status: 'all' },
};

export function parseInitialState(initialState: string | undefined): AppState {
  if (!initialState) return DEFAULT_STATE;
  try {
    const parsed = JSON.parse(initialState) as Partial<AppState>;
    return { ...DEFAULT_STATE, ...parsed };
  } catch {
    // Malformed or from an incompatible app version — fall back to defaults.
    return DEFAULT_STATE;
  }
}

export function useAppState() {
  const [api, setApi] = useState<HostAppAPI | null>(null);
  const [state, setState] = useState<AppState>(DEFAULT_STATE);
  const apiRef = useRef<HostAppAPI | null>(null);

  useEffect(() => {
    connectToHostApp()
      .then(({ api: resolvedApi, initialState }) => {
        apiRef.current = resolvedApi;
        setApi(() => resolvedApi);
        setState(parseInitialState(initialState));
      })
      .catch(() => {
        // connectToHostApp rejects when there's no Fusion parent window to
        // connect to (e.g. opening the raw Vite dev URL directly instead of
        // through Fusion). api and state simply stay at their initial
        // values (null / DEFAULT_STATE) — nothing else to do here.
      });
  }, []);

  return { api, state, setState, apiRef };
}

Read the full file on GitHub · 230 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. 2mo ago First seen · 230 lines · 94 tokens per session scan A ff9d68070eb0

Subscribe to this mod's changes

handle-startup-state is a skill published in the GitHub repository cognitedata/builder-skills (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 94 tokens to every session and 2,013 once invoked, about $0.0004 per session on Opus 5.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-09-05.

Related

handle-startup-state compared with skills from other repositories

handle-startup-state next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
handle-startup-statecognitedata/builder-skillsSkill6yesterdayApache-2.0A94Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code