ClaudeSuperPower
SubmitLog in
S

SessionStart

Hook

SessionStart nudge directing the agent to delegate data-engineering tasks to altimate-code via the altimate-code skill. The UserPromptSubmit pre-run hook was removed because it double-invoked altimate-code (once at hook time, once when the model fired the skill), doubling token consumption on the al

0Other

Fires on

SessionStart

Once, as a session begins — before you type anything.

Where this sits in a session

  1. Session start→
  2. Prompt submitted→
  3. Prompt expansion→
  4. Before tool use→
  5. After tool use→
  6. Notification→
  7. Before compaction→
  8. Subagent finished→
  9. Turn finished→
  10. Session end

Observes only — Emits messages or context. It never returns a permission decision.

What it runs

Executed automatically when the event fires — no prompt, no confirmation.

command
bash "${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-start.sh"

Install it yourself

Paste into .claude/settings.json to run this hook without installing the whole plugin. Adjust the paths to point at your own copy of the scripts.

settings.json
{
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "bash \"${CLAUDE_PLUGIN_ROOT}/hooks-handlers/session-start.sh\""
          }
        ]
      }
    ]
  }
}

Source

Read this before installing — it runs on your machine with your permissions.

#!/usr/bin/env bash
# SessionStart hook for the altimate-code plugin. Emits a descriptive statement
# of the altimate-code skill's capabilities so Claude can route to it when the
# task shape fits. Deliberately descriptive rather than imperative — see the
# Claude plugin review-criteria checklist items on "avoid instructing Claude
# to call other tools" and "don't interfere with tool sequencing."
#
# Uses printf (not a here-doc) so the hook works in restricted sandboxes that
# refuse to create the temporary file a here-doc needs.

printf '%s\n' '{'
printf '  "hookSpecificOutput": {\n'
printf '    "hookEventName": "SessionStart",\n'
printf '    "additionalContext": "The altimate-code plugin ships two skills in this session. (1) The `altimate-code` skill routes data-engineering work to the altimate-code CLI — column-level lineage, downstream-impact, cross-database validation, FinOps, PII from sampled rows, query cost attribution, schema diffs, dev-vs-prod diffing. It is not well-suited for pure file/code edits to dbt models and SQL files that do not touch warehouse state — native Bash/Edit/Write handles those faster. (2) The `review` skill runs the altimate-code dbt PR reviewer on dbt project changes (models/**.sql, schema.yml, dbt_project.yml, sources.yml, macros, snapshots, seeds). It emits a signed verdict envelope with column lineage, query equivalence, dbt anti-pattern detection, and PII screening — none of which native tools or a generic code-review skill can compute. When the user asks to review dbt / SQL / warehouse changes, this is the specialized reviewer available. For non-dbt code review (TypeScript, Python, Go), the `review` skill declines."\n'
printf '  }\n'
printf '}\n'

Shipped by 1 plugin

Installing any of these installs this hook.

altimate-code3

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just hooks.

Subagents

All subagents →

claude-security

The dedicated Claude Security orchestrator. Hand it an unattended job — "fully scan this repository and patch what you find; I understand it will use a lot of tokens" — and it runs the whole thing itself: capturing the revision, driving the multi-agent scan through the claude-security:scan workflow,

32.8K stars

bedrock-sme

Amazon Bedrock subject matter expert emphasizing cost-efficient usage patterns. Use when designing Bedrock-based solutions, selecting models, architecting agent workflows, configuring knowledge bases, or when you need practical Bedrock guidance that won't blow the budget.

oauth-oidc-specialist

Expert in OAuth 2.0 and OpenID Connect protocol specifications, security best practices, and compliance. Specializes in flow selection, token security, protocol-level debugging, and standards compliance. Use for protocol design decisions, security reviews, and debugging token/auth flows at the HTTP