type: queue-operation

operation: enqueue

content:
reply with the single word OK
echo "-- cursor-agent status:"
timeout 60 cursor-agent status 2>&1 | grep -iE 'logged|auth|email|status|error' | FT_FROM_HOOK=1 ft head -5


hookEvent: SessionStart

stderr: Failed with non-blocking status code: /bin/sh: 1: /home/user/Projects/slopgate/.worktrees/fix/record-string-any-regex-performance/hooks/session-start.sh: not found

type: attachment

userType: external

entrypoint: sdk-cli

gitBranch: HEAD


hookEventName: SessionStart

additionalContext: STRUCTURED TASK LIST: your TaskCreate/TaskUpdate tasks persist on disk across compaction — call TaskList to see current open tasks; do NOT assume they were lost.


content: STRUCTURED TASK LIST: your TaskCreate/TaskUpdate tasks persist on disk across compaction — call TaskList to see current open tasks; do NOT assume they were lost.

hookName: SessionStart

toolUseID: SessionStart


type: user

role: user

permissionMode: auto

promptSource: sdk


addedNames: CronCreate CronDelete CronList DesignSync EnterWorktree ExitWorktree NotebookEdit PushNotification RemoteTrigger SendMessage TaskCreate TaskGet TaskList TaskOutput TaskStop TaskUpdate WebFetch WebSearch


addedTypes: claude code-reviewer dead-advisor Explore general-purpose Plan security-guard statusline-setup

addedLines: - claude: Catch-all for any task that doesn't fit a more specific agent. FleetView's default when no agent name is typed. (Tools: *)

addedLines:
- code-reviewer: Use this agent when a major project step has been completed and needs to be reviewed against the original plan and coding standards. Examples: <example>Context: The user is creating a code-review agent that should be called after a logical chunk of code is written. user: "I've finished implementing the user authentication system as outlined in step 3 of our plan" assistant: "Great work! Now let me use the code-reviewer agent to review the implementation against our plan and coding standards" <commentary>Since a major project step has been completed, use the code-reviewer agent to validate the work against the plan and identify any issues.</commentary></example> <example>Context: User has completed a significant feature implementation. user: "The API endpoints for the task management system are now complete - that covers step 2 from our architecture document" assistant: "Excellent! Let me have the code-reviewer agent examine this implementation to ensure it aligns with our plan and follows best practices" <commentary>A numbered step from the planning document has been completed, so the code-reviewer agent should review the work.</commentary></example>
 (Tools: All tools)

addedLines:
- dead-advisor: Fallback for the built-in `advisor` tool when its API is failing. A reusable, session-persistent stronger-reviewer (opus, xhigh effort) that reconstructs the main agent's full conversation from the on-disk transcript and gives the same critical advice the `advisor` tool would. Spawn via the `/dead-advisor` skill, then continue across the session via SendMessage. Do NOT invoke directly — the skill supplies the disambiguating transcript marker this agent needs.
 (Tools: All tools)

addedLines: - Explore: Read-only search agent for broad fan-out searches — when answering means sweeping many files, directories, or naming conventions and you only need the conclusion, not the file dumps. It reads excerpts rather than whole files, so it locates code; it doesn't review or audit it. Specify search breadth: "medium" for moderate exploration, "very thorough" for multiple locations and naming conventions. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)

addedLines: - general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)

addedLines: - Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, Artifact, ExitPlanMode, Edit, Write, NotebookEdit)

addedLines:
- security-guard: Independent, adversarial pre-ship / pre-merge security + correctness review of a specific file, route, or diff. Invoke as a FRESH cross-context pass — especially after a self-audit has "converged" or a change is about to ship — to catch what a self-review stops looking for: object-level authorization (IDOR), fail-open auth/crypto paths, side-channel/timing oracles, injection, SSRF, DoS, idempotency/atomicity, content-type confusion, and info-disclosure defects. Give it the exact file(s) or diff to review. Language- and platform-agnostic — works on any codebase with a trust boundary (web/API, CLI, library/SDK, mobile or desktop backend, infra/IaC, data pipeline, smart contract).

<example>Context: a change is about to merge after the author already reviewed it. user: "complete.ts is ready to ship — the attachment upload route." assistant: "Before merge, let me run the security-guard agent as an independent adversarial pass over complete.ts." <commentary>Pre-ship gate on a specific route — the security-guard's core job is the fresh-eyes catch the author's converged review missed.</commentary></example>
<example>Context: a multi-wave audit reported clean. user: "the audit converged, no more P0/P1." assistant: "Convergence on a self-audit is exactly when a fresh independent pass earns its place — running security-guard over the changed routes." <commentary>The documented failure mode: a converged self-audit stops hunting; an independent pass finds the residual miss.</commentary></example>
 (Tools: All tools)

addedLines: - statusline-setup: Use this agent to configure the user's Claude Code status line setting. (Tools: Read, Edit)


content:
- agent-doc-authoring: Use when writing or editing any document AI agents will read — CLAUDE.md, AGENTS.md, specs, standards, plans, skill files (SKILL.md), subagent/system prompts. Also when a doc carries private codenames or nicknames, reads as prose narrative instead of imperatives, or needs naming/wording decisions for an agent audience. Read before writing the doc; check the diff against it before declaring the doc done.
- agentify-doc: Use when asked to rewrite, compress, tighten, condense, shorten, or "agentify" an existing skill (SKILL.md), CLAUDE.md, spec, standard, plan, or agent/system prompt — or when such a doc is verbose, prose-heavy, token-bloated, duplicated, or full of filler for an agent audience. Triggers on "make this leaner for agents", "cut tokens from this doc", "rewrite this skill concisely", "tokenomics", "agentify".
- ask-codex: Use when delegating a task to Codex CLI (OpenAI coding agent) via `cdx exec` — second opinion, code review, deep diagnosis, research, or implementation. Triggers on /ask-codex, "ask codex", "ask gpt", "second opinion from codex/gpt-5", "have codex review/implement/investigate this". Parses optional model/effort spec (e.g. 5.6-terra/high), builds prompt, calls cdx exec directly — never through a dispatched subagent.
- astro: Astro+React island projects. Enforces hydration directive selection, provider context across island boundaries, SSR-safe react-query, SEO-preserving patterns. Triggers on *.astro, astro.config.*, React islands, @astrojs/react config edits.
- babysit-runplan: Use when user asks to run/watch/babysit a run-plan — "run the plan", "babysit the runplan", "is the plan still running", "the run died, continue it" — or when a foreground runplan turn returns. Owns the launch-consume-branch loop; branches every failure on failureClass; only wrapper-engine-down is retriable.
- brainstorm: You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- caveman: Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
- ci-cd-expert: Set up or fix efficient CI/CD on a self-hosted runner sharing a dev workstation — PR-gated trunk, shared build cache, CPU containment, flaky-gate diagnosis, browser/E2E matrix gates (sharding, completeness accounting, fake-green detection). Use when adding CI to a project, when a gate is slow/flaky/starving the machine, when a gate reads green but catches nothing, or when replicating the platform repo's CI stack elsewhere.
- claudex-workflow: Run multi-agent work in Claudex via the Workflow tool with gpt models (luna/sol/terra). Use when the user asks for a dyn-wf, a dynamic workflow, parallel subagents, or names a gpt model for coding or review.
- cloudflareops: Use for any Cloudflare operation — deploying Workers, wrangler commands, secrets, R2/D1/KV/Hyperdrive, cron triggers, Queues, Pages-vs-Workers decisions, Cloudflare Images, log tailing, or capacity/latency problems on the bundled plan. Picks MCP vs wrangler vs REST API before falling back to dashboard clicks. Triggers on "deploy worker", "wrangler", "cloudflare", "R2 bucket", "D1", "KV namespace", "worker secret", "cron trigger", "queue costs".
- code-quality-reviewer: Use when reviewing implementation code for quality after spec compliance passes — checks structure, cognitive load, performance, maintainability, and seam/contract integrity for `@platform-modules/*`.
- creating-journey-e2e-tests: Use when deriving an outcome-asserting end-to-end test from a user-journey contract (a UJ-NNN doc or equivalent flow spec) — turning a documented happy path + failure/permission branches into a Playwright (or similar) spec that actually catches UI and flow bugs. The derivation pass that follows create-journeys. Triggers on "write the E2E for this journey", "derive a test from UJ-0NN", "make a real outcome test for the purchase flow".
- creating-mockups: Browser-based visual brainstorming companion for UI mockups, wireframes, and layout comparisons. Invoke only when user needs to see visual options — not for text/conceptual choices.
- creating-ui-matrix-tests: Use when building granular per-page, per-role UI-element regression tests — asserting every button is clickable/disabled when it should be, every input/textarea/table/form renders per role, catching small UI regressions a flow test misses. Distinct from journey/flow tests. Ships a manifest-driven matrix harness template plus a deterministic validator that fails closed on rotted selectors, routes, and roles.
- dead-advisor: Use when the built-in `advisor` tool fails with an API/network/server error and you still want a stronger-reviewer critique. Triggers on /dead-advisor, "advisor is dead", "advisor API error", "advisor keeps failing", "fallback advisor". Spins up (once per session) a reusable fable medium effort advisor subagent that reconstructs your full conversation from the on-disk transcript and returns the same kind of senior advice the `advisor` tool would, then continues via SendMessage on later calls.
- debug: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- dispatching-parallel-agents: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- finishing-a-development-branch: Use when development is complete and verified — lands the feature branch (merge-to-main or open-a-PR, per project) and cleans up the worktree via the tested shared brain. Resolves conflicts by agent judgment; NEVER prompts the user.
- handoff: Use when ending a session to create a handoff document so a fresh agent can continue the work
- learn-from-mistakes: Use when a session ends or user invokes /learn-from-mistakes
- memory-gc: Use to audit and prune persistent memory — "is this memory still valid", "clean up memory", "are these memories stale", "memory gc", periodic memory hygiene, or after large refactors/audits that likely invalidated recorded facts. Verifies each memory's claims against live repo/tool state, classifies CONFIRMED/SUSPECT/CONFLICTING/UNVERIFIABLE, updates or deletes with user sign-off on deletions.
- pickup: Use when session opens with a bare continuation prompt — "resume", "continue", "continue from where you left off", "pick up where we were", "what were we doing" — or any restart after /clear, /compact, or crash where the user gives no task detail. Deterministically re-derives session state from git, run-plan journal, background tasks, handoff docs, and the on-disk transcript BEFORE acting. Never blind-continue.
- plan: Use when you have a spec or requirements for a multi-step task, before touching code
- plan-inventory: Use when the user asks what plans exist and their states — "which plans are ready to run", "which are abandoned", "what's running right now", "list our plans", "which plan should I test on" — or when another skill needs a plan slug the user didn't supply. Classifies docs/plans/* + runstate journals into running / ready / stalled / done / abandoned with a suggested action each.
- plan-preflight: Use before launching any run-plan/workflow execution to drain every human decision out of the plan upfront — "release all blockers before running", "will this HALT on anything?", "preflight the plan", "make this plan run unattended overnight". Scans plan for HALT-shaped items (irreversible ops, requires_decision tasks, ambiguous scope, missing creds), batches all questions into one AskUserQuestion round, bakes answers into the plan.
- prod-env: Production-environment doctrine for agents — how to PLAN a prod env, SET UP a prod env, or WORK IN a live prod env. Use when task involves creating/designing production infrastructure, deploying to production, cutting over a domain, touching live data/secrets/migrations, or when user says "production", "go live", "prod env", "deploy to prod". Router — loads one of three docs by task type.
- run-plan: Use when the user runs "/run-plan <PLAN_SLUG>" or when any skill needs to execute or resume a plan — unified plan executor. Single engine: released v2 bundle (`runplan` on PATH → `~/.harness/engine/versions/<CURRENT>`), fail-closed, resumable via its own journal. Single entry point; replaces /resume-plan.
- security-gate: Use as a pre-ship / pre-merge security + correctness gate on a payments or financial module, route, or diff — especially after a self-audit has "converged". Runs two legs (a deterministic complete-mediation oracle + a single-roll gpt-5.6-sol/low adversarial LLM review; k=1 floor validated on gpt-5.4/low, not yet re-validated on gpt-5.6-sol) over the target AND its pulled-in critical imports, then merges. Triggers on "review before merge", "is this payment path safe", "audit this webhook/refund/payout/ledger code", "did the self-review miss anything", "IDOR", "self-deal", "complete mediation", "missing authorization check" (the complete-mediation-scan procedure lives in references/). Re-validated 2026-07-02 (supersedes the older sonnet/medium k≥3 config — see VALIDATION.md).
- ship: Use when the user invokes /ship or asks to execute an implementation plan in-session with subagents — wave-based dispatch (fresh implementer per task), two-stage review (spec compliance then code quality), automated verification, then land via the project's frozen ship.sh. In-session interactive strategy only — for unattended, resumable, or multi-wave engine runs use run-plan; for trivial single-wave sequential plans use run-plan's inline fallback.
- ship-it: Use when user sends a terse landing command — "push", "push deploy", "commit and push", "ship it", "land this", "clean up the worktree and branch", "wrap up" — and expects the full gate→commit→land→deploy→cleanup chain without spelling it out. Runs verification gates, commits, lands per project rule, deploys where push=deploy, cleans worktrees.
- skill-creator: Use when creating a skill from scratch, editing or improving an existing skill, verifying a skill works before deployment, running evals against a skill, benchmarking skill performance with variance analysis, or optimizing a skill's description for better triggering accuracy.
- slopgate-improve: Mine a project's institutional memory (skills, agents, commands, CLAUDE.md, editor rules) for conventions not yet caught by slopgate, and add them to the right rule tier. Invoke on /slopgate-improve or when a recurring agent mistake is documented but undetected.
- slopgate-init: Onboard any repo to the global slopgate engine. Detect stack, mine the project's OWN local conventions (.claude/skills|agents|commands + CLAUDE.md subtree + editor rules), evaluate which are statically-detectable rule candidates, author the project rule pack, drive violations to zero, wire + verify hooks. Use when adopting slopgate in a new project or re-evaluating an existing project's rules.
- slopgate-ux: Inject the ANTI-SLOP UX framework as design directives before generating or modifying any UI. Enforces complete states, action hierarchy, feedback loops, accessibility, performance, and human-centric microcopy — the semantic UX rules a static scanner cannot catch. Use before building or editing components, pages, forms, modals, tables, or any user-facing interface. Complements the slopgate `ux:{}` static rule module (which gates the mechanical subset).
- tdd: Use when implementing any feature or bugfix, before writing implementation code
- threejs-animation: Three.js animation - keyframe animation, skeletal animation, morph targets, animation mixing. Use when animating objects, playing GLTF animations, creating procedural motion, or blending animations.
- threejs-fundamentals: Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
- threejs-geometry: Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
- threejs-interaction: Three.js interaction - raycasting, controls, mouse/touch input, object selection. Use when handling user input, implementing click detection, adding camera controls, or creating interactive 3D experiences.
- threejs-lighting: Three.js lighting - light types, shadows, environment lighting. Use when adding lights, configuring shadows, setting up IBL, or optimizing lighting performance.
- threejs-loaders: Three.js asset loading - GLTF, textures, images, models, async patterns. Use when loading 3D models, textures, HDR environments, or managing loading progress.
- threejs-materials: Three.js materials - PBR, basic, phong, shader materials, material properties. Use when styling meshes, working with textures, creating custom shaders, or optimizing material performance.
- threejs-postprocessing: Three.js post-processing - EffectComposer, bloom, DOF, screen effects. Use when adding visual effects, color grading, blur, glow, or creating custom screen-space shaders.
- threejs-shaders: Three.js shaders - GLSL, ShaderMaterial, uniforms, custom effects. Use when creating custom visual effects, modifying vertices, writing fragment shaders, or extending built-in materials.
- threejs-textures: Three.js textures - texture types, UV mapping, environment maps, texture settings. Use when working with images, UV coordinates, cubemaps, HDR environments, or texture optimization.
- ui-designer: Use when building, restyling, reviewing, or polishing any UI in this project — components, pages, tokens, motion, loading states, typography, color — or when a task references the UI overhaul, a design template ("premium", "futuristic"), or asks whether a screen "feels" right.
- using-git-worktrees: Use when starting implementation work that needs branch isolation — creates a .worktrees/ workspace before ship executes tasks
- ux-designer: Design good UX for apps . Inject the ANTI-SLOP UX framework as design directives before generating or modifying any UI. Enforces complete states, action hierarchy, feedback loops, accessibility, performance, and human-centric microcopy — the semantic UX rules a static scanner cannot catch. Use before building or editing components, pages, forms, modals, tables, or any user-facing interface. Complements the slopgate `ux:{}` static rule module (which gates the mechanical subset).
- webapp-testing: Playwright toolkit for local webapp testing. Verify frontend, debug UI, capture screenshots, view browser logs.
- workflow-router: Use when choosing which executor/orchestrator/model to route a task to — "which tool should handle this", "route this task", before dispatching any implementation/review/plan-execution work, or whenever tempted to hand-pick a model or invoke an agent CLI raw. One routing table = the established daily-workflow defaults; consult it INSTEAD of improvising a dispatch.
- accessibility: Run a pa11y accessibility scan on a URL and provide actionable recommendations. Use when asked for "accessibility" scan/report/audit or a full site report.
- canvas-design: Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
- componentizer: Componentizer
- create-journeys: Use when exploring an application to document user journeys, role-based workflows, actor surfaces, executable journey contracts, or a testable journey catalog.
- deploy-nextjs-cloudflare: Deploy Next.js to Cloudflare Workers (via OpenNext)
- extract-vision: Reconstruct a project's VISION.md from what the user actually typed into Claude Code prompt boxes over the project's life — real user messages + AskUserQuestion answers, separated from subagent/headless/harness noise, SYNTHESIZED into a coherent vision document. Use on /extract-vision <project-path>, "what did I say I wanted for X", "rebuild the vision from my prompts", or before writing GOLIVE/roadmap docs for a project whose intent lives only in chat history.
- extracting-fable: Use when you want to reverse-engineer a model's working signature (narration, authoring, decision style) from local Claude Code transcripts on a machine that ran it — e.g. recreate the Fable corpus/KB/mode-skill on another PC, mine "what would Fable do", or build an imitation-mode skill for any model. Triggers on "extract fable", "mine fable from logs", "rebuild the fable corpus", "redo the fable analysis here".
- fix-rot: Use when an agent shows compaction rot / context rot — lost the plot after a compact/summarize, forgot the session goal, repeating done work, ignoring standing user instructions, drifting from methodology, confused about what's next. Triggers on /fix-rot, "you've lost context", "refresh your context", "you forgot what we're doing", "re-read the conversation", "recover the session", "you're rotting", "reorient yourself". Reconstructs session goals, methodology, philosophy, user intent/directions/instructions, active/deferred/remaining tasks, what's gated on the user, and a prioritized immediate TODO — WITHOUT re-polluting the main thread. Emits the recovered context as a resumable harness-native JSONL (`docs/plans/`, keyed by a session slug) so `[[handoff]]` / `[[run-plan]]` continue it in another session.
- ft: Run this shell command and show the output:
- ft-probe: Run this shell command and show the exact output:
- improve-codebase-architecture: Find deepening opportunities in codebase, informed by domain language in CONTEXT.md and decisions in docs/adr/. Use when user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make codebase more testable and AI-navigable.
- mobile-ux: Treat this like phone design, not screen design. The user is holding an iPhone Pro Max one-handed.
- trello: Use for Trello — list boards/lists/cards, create/move cards, complete tasks, execute TODO→DONE workflow via REST API.
- vibeflare: Use when working with the vf CLI (VibeFlare command-line client) — running chat/completions from the shell, piping, scripting, login/setup, config env vars (VIBEFLARE_URL/KEY/MODEL), or debugging vf usage errors. Also covers VibeFlare REST API integration, API keys, and SDK/fetch embedding (references/api.md). Triggers on "vf", "vibeflare", "vf login", "vf not working", "vibeflare API".
- visual-plan: Create an interactive Agent-Native visual plan for the current task.
- wrap-up: End-of-session checklist for shipping, memory, and self-improvement
- security-sweep: Map a repo's attack surface, then run an isolated adversarial security-guard review per high-risk unit with cross-model verification. Depth-per-unit, never whole-repo-at-once — the structure that catches what a converged self-audit misses.
- dataviz: Use this skill whenever you are about to create ANY chart, graph, plot, dashboard, or data visualization, in ANY output medium — an HTML or React artifact, inline SVG, plotting code in any library (matplotlib, plotly, d3, Recharts, …), an image/PNG you will render and upload, or a chart shared into Slack. Read it BEFORE writing the first line of chart code, choosing chart colors, building a stat tile / meter / KPI row, or laying out a dashboard. Produces visualizations that read as one system — elegant, accessible, consistent in light and dark — using a brand-neutral placeholder palette you swap for your own. Teaches a design-system-agnostic method: a form heuristic, a color formula with a runnable validator, mark specs, and interaction rules. A validated default palette is documented in `references/palette.md` — swap that file's values for your brand's. Triggers on: "chart", "graph", "plot", "data viz", "visualization", "dashboard", "analytics", "visualize data", "categorical colors", "sequential / diverging palette", "stat tile", "sparkline", "heatmap", "legend", "axis", "tooltip", "chart colors", "color by series".
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- simplify: Review the changed code for reuse, simplification, efficiency, and altitude cleanups, then apply the fixes. Quality only — it does not hunt for bugs; use /code-review for that.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m) - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled cloud agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring cloud agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration.
TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens).
SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a GitHub pull request; for your working diff use /code-review
- security-review: Complete a security review of the pending changes on the current branch

names: agent-doc-authoring agentify-doc ask-codex astro babysit-runplan brainstorm caveman ci-cd-expert claudex-workflow cloudflareops code-quality-reviewer creating-journey-e2e-tests creating-mockups creating-ui-matrix-tests dead-advisor debug dispatching-parallel-agents finishing-a-development-branch handoff learn-from-mistakes memory-gc pickup plan plan-inventory plan-preflight prod-env run-plan security-gate ship ship-it skill-creator slopgate-improve slopgate-init slopgate-ux tdd threejs-animation threejs-fundamentals threejs-geometry threejs-interaction threejs-lighting threejs-loaders threejs-materials threejs-postprocessing threejs-shaders threejs-textures ui-designer using-git-worktrees ux-designer webapp-testing workflow-router accessibility canvas-design componentizer create-journeys deploy-nextjs-cloudflare extract-vision extracting-fable fix-rot ft ft-probe improve-codebase-architecture mobile-ux trello vibeflare visual-plan wrap-up security-sweep dataviz update-config keybindings-help simplify fewer-permission-prompts loop schedule claude-api run init review security-review


type: last-prompt

lastPrompt: reply with the single word OK echo "-- cursor-agent status:" timeout 60 cursor-agent status 2>&1 | grep -iE 'logged|auth|email|status|error' | FT_FROM_HOOK=1 ft head -5


type: message

role: assistant

type: thinking

service_tier: standard

speed: standard

type: assistant

effort: high


Bash

command: echo "-- cursor-agent status:"; timeout 60 cursor-agent status 2>&1 | grep -iE 'logged|auth|email|status|error' | FT_FROM_HOOK=1 ft head -5

description: Check cursor-agent auth status

type: direct


hookEvent: PreToolUse

stderr: Failed with non-blocking status code: /bin/sh: 1: /home/user/Projects/slopgate/.worktrees/fix/record-string-any-regex-performance/hooks/commit-hook.sh: not found


stderr: Failed with non-blocking status code: /bin/sh: 1: /home/user/Projects/slopgate/.worktrees/fix/record-string-any-regex-performance/hooks/baseline-guard.sh: not found


content:
-- cursor-agent status:
✓ Logged in as royachiron@gmail.com


type: text

text: OK — `cursor-agent` logged in as royachiron@gmail.com.