LogoAhaPrompt
  • Prompts
  • Featured
  • Models
  • Submit
  • Blog
AhaPromptAhaPrompt

AI Prompts for Images, Video & Audio — Every Model, One Library

Built withLogoNEXTY.DEV
Explore
  • All Prompts
  • Featured Prompts
  • Image Prompts
  • Video Prompts
  • Audio Prompts
  • AI Models
  • Submit a Prompt
  • Blog
Languages
  • English
  • 中文
  • 日本語
  • 한국어

Copyright © 2026 AhaPrompt All rights reserved.

Privacy PolicyTerms of Service
HomeAI Prompt LibraryAI Video PromptsModel Routing Setup Prompt

Model Routing Setup Prompt

OpenAIGPT-6 AstraOpenAIvideo

Set up model routing for this repo: 1. List this month's task types and how long each answer was. Table only, change nothing 2. Anything that ended past 128K goes to Gemini 4 Argon as one call, no chunking > Terminal and shell work stays on Opus 5.5 > Fixes that failed twice go to GPT-6 Astra > Cache the repo context on Argon so every run reuses it 3. Price each task type at Argon's intro rate next to what it costs today 4. Print the routing table with the price column, then wait for my yes before switching anything.

Details
Type
AI Video Prompts
Aspect Ratio
4:5
Duration
0:25
Updated
Oct 3, 2026
Category
AdvertisingRealisticMinimalist
Source

How to use this prompt

  1. 1Copy the full prompt with the copy button above.
  2. 2Open GPT-6 Astra by OpenAI, or your preferred AI video generator.
  3. 3Paste the prompt and keep the camera and motion terms — they steer the cinematography.
  4. 4Match the example's settings (4:5 · 0:25 · Advertising · Realistic · Minimalist), then iterate — small wording changes shift the output a lot.

Frequently asked questions

Which AI model generated this video?

This clip was generated with GPT-6 Astra by OpenAI. The prompt on this page is the exact text used to create it.

What settings does this prompt use?

The example was generated with GPT-6 Astra using: 4:5 · 0:25 · Advertising · Realistic · Minimalist. Reusing these settings gives the closest match.

How do I get similar results?

Copy the prompt as-is first, then change the subject while keeping the camera, motion, and lighting terms. Video models are sensitive to wording, so expect a few runs.

Can I modify this prompt?

Yes. Prompts work best as starting points — swap scenes, adjust pacing terms, or change the aspect ratio to fit your project.

More GPT-6 Astra prompts

2:20
OpenAIGPT-6 Astra
In LilyPond, write a fugue for organ in E major without ever using the note E (or its enharmonic spellings).
Details
0:20
OpenAIGPT-6 Astra
Act as a security engineer reviewing a repository Analyze the supplied scanner findings and affected source files Prioritize exploitable issues over informational warnings For each confirmed issue, provide the root cause, affected location, minimal patch, and regression test Do not invent vulnerabilities or claim a fix passed without test evidence Never expose secret values in the report
Details
0:25
OpenAIGPT-6 Astra
Configure my Codex workspace for hierarchical model selection and subagents: 1. Audit ~/.codex/agents and .codex/agents for subagent profiles fitting lead, workers, and adversary: > Give explorer, worker, and researcher model = 'gpt-6-luna', model_reasoning_effort = 'medium' > Assign worker an isolated git worktree branch to eliminate concurrent file conflicts > Create .codex/agents/adversary.toml with model = 'gpt-6-astra' (upgradeable to 'gpt-6.1-astra'), model_reasoning_effort = 'high', sandbox_mode = 'read-only' 2. Configure model selection in ~/.codex/config.toml: [session] model = 'gpt-6.1-sol' model_reasoning_effort = 'high' [agents] default_subagent_model = 'gpt-6-luna' default_subagent_reasoning_effort = 'medium' max_concurrent_threads_per_session = 8 3. Verify environment variables and routing: check for flags overriding reasoning effort or disabling multi-agent tools. Report them, change nothing 4. Add automatic delegation rules to AGENTS.md: > Summon @ adversary before finalizing multi-file architecture plans > Automatically trigger @ adversary when a test or compiler error repeats twice > Enforce @ adversary contract audit before declaring tasks complete or staging git commits Show every configuration diff first. Do not apply edits until confirmed
Details
0:47
OpenAIGPT-6 Astra
Build a Chrome extension called Signal Crawler using Manifest V3. The extension should help me find business problems in public web pages. It must work on the page I have open, not silently crawl other sites. CORE EXPERIENCE When I click the extension icon, a small animated crawler appears on the page. It moves between readable text blocks, visually scans them and highlights useful passages. A floating panel shows what it has found in real time. Clicking the icon again removes the crawler, panel, highlights and all changes to the page. WHAT TO ANALYZE Support three source types: 1. Job posts: look for manual, repetitive work, slow workflows and tasks that could be automated. 2. Customer reviews: look for repeated complaints, workarounds, missing features and problems that cost the customer time or money. 3. Product and company pages: look for what the business sells, who it serves and how a proposed fix could fit its existing workflow. Ignore navigation, ads, cookie banners, forms, code blocks and hidden text. Handle pages that load more content while scrolling. THE CRAWLER Draw the crawler on a transparent canvas above the page without blocking clicks or text selection. Give it a compact body, eight jointed legs and visible stepping motion. It should move automatically from one relevant text block to another. When it finds a useful passage, pause briefly, place a foot near it, highlight the passage and send a small animated signal from that passage to the floating panel. Use a restrained visual style: warm yellow for findings, white for the body, dark outlines and a subtle glow. Movement should feel quick and alive, but the text must remain readable. SIGNAL BOARD For each finding, show: - the exact quote - the page title and URL - the type of signal - the problem it suggests - how many similar signals have been found Group related findings into clusters. Do not treat one isolated sentence as a proven market. Make repeated evidence visually more prominent than single mentions. ASTRA ANALYSIS Add an optional GPT Astra analysis step. The user enters their own API key and model name in the extension settings. Store the key locally and make API requests from the background service worker, never from the page. For each cluster, ask Astra to produce: - a plain-English description of the problem - who experiences it - evidence for why it matters - the smallest plausible fix - a short draft offer - what still needs human verification Astra must not invent quotes, companies, prices or customer counts. Every conclusion in the panel should link back to its source passages. PANEL CONTROLS Include Pause, Resume, Analyze, Copy Findings, Export JSON, Clear and Close. The panel should show scanning progress, the number of passages checked, findings collected and clusters formed. Let me open any finding and jump back to its original position on the page. QUALITY REQUIREMENTS The extension must not break scrolling, links, page layout or text selection. It should not send messages, contact companies or publish anything automatically. On Close, remove every canvas element, highlight, listener, observer and timer. Support reduced-motion preferences. Handle API failures by keeping the collected evidence visible. Use plain JavaScript, HTML and CSS. Provide every file needed for a working Manifest V3 extension, then give me clear installation and testing steps.
Details
0:26
OpenAIGPT-6 Astra
Rebuild my Codex setup around this tree: • Configure persistent dot agent on GPT-6 Astra with cloud container and headless browser access • Set up workspace bridges to route routine dev logs to files and critical architectural gates to Slack • Delegate multi-file coding tickets to local Codex CLI environments with automatic task locking • Add one rule to AGENTS.md: pause autonomous execution and request manual take-over before modifying external infrastructure or security configs Show every change as a diff first. No edits until I say go
Details
0:17
OpenAIGPT-6 Astra
ROLE AND OBJECTIVE You are an elite motion-design studio composed of a creative director, senior 3D artist, motion graphics designer, cinematographer, lighting artist, technical animator, compositing artist, and sound designer. Reconstruct the supplied 16.55-second Sanctum / INF launch advertisement with extremely high visual fidelity. Your goal is a professional, broadcast-quality, 16:9 motion-design film that matches the reference video in its visual identity, animation language, camera choreography, pacing, compositions, transitions, typography, dimensional materials, and overall sense of polish. Do not create a generic cryptocurrency commercial. Reproduce the distinct artistic decisions of the reference. Study the reference video before producing anything. It takes priority over any approximate parameters in this specification. The final animation must feel intentionally designed and directed, not like a sequence of unrelated AI-generated clips. TECHNICAL DELIVERY SPECIFICATION Target duration: 16.55 seconds. Aspect ratio: 16:9. Master render resolution: 3840 × 2160. Working preview resolution: 1920 × 1080. Frame rate: 24 FPS. Progressive scan. High-quality antialiasing. Physically based 3D rendering. Consistent color management across shots. Carefully controlled bloom, reflections, depth of field, and motion blur. No unintended frame interpolation or discontinuity. Continuous audio with synchronized sound design. Final output: high-bitrate H.264/H.265 MP4. Preserve editable source files, assets, and animation timelines. AESTHETIC IDENTITY Create an exceptionally polished visual language combining premium 3D brand animation, futuristic financial-product storytelling, playful geometric composition, and cinematic lighting. The design should feel: Vibrant but controlled. Youthful but premium. Technically sophisticated yet friendly. Visually playful without being childish. High-energy but never chaotic. Glossy and dimensional rather than flat. Full of subtle optical effects, translucency, and colorful reflections. Combine two distinct worlds. WORLD A — BRIGHT IRIDESCENT BLUE: An immersive bright electric-blue gradient environment with cyan, sapphire, and subtle greenish or pastel illumination. The background contains large soft gradients, gently fluctuating light, and faint atmospheric texture. Floating glossy black INF tokens exist at different depths, some small and distant, others enormous and partially cropped by the boundaries. Small decorative geometric particles float among the tokens: four-pointed sparkles, soft concave diamond shapes, neon-green stars, yellow and orange squares, tiny magenta pieces, and white reflective accents. There is no literal room, landscape, ground plane, horizon, or architectural structure. The camera occupies an abstract, infinite, dimensional space. WORLD B — DARK CINEMATIC STUDIO: A nearly black or midnight-navy void illuminated with luminous cobalt, violet, and cyan spotlights. Subtle floor reflections suggest a glossy studio floor beneath the objects. Soft pools of blue light create grounding without introducing recognizable walls. Objects cast soft shadows and contribute reflected light to nearby surfaces. The scene has dimensional volume, controlled darkness, and pronounced separation between background and glowing 3D elements. Never use a simple black solid as the only environmental treatment. Preserve nuanced lighting, ambient diffusion, and slight colored atmospheric depth. CORE OBJECT DESIGN — INF TOKEN Model the primary INF token as a thick, glossy, circular 3D coin. GEOMETRY: Circular silhouette with significant visible thickness. Rounded edge bevel. Smooth polished cylindrical outer wall. Dark black or charcoal material. Slight glossy edge highlights. A circular face with a centered abstract INF graphic. FACE ARTWORK: A soft, multi-lobed, organically curved shape. Intersecting or overlapping rounded color fields. Iridescent gradient regions flowing from pastel lavender and blue into cyan, vivid lime, yellow, orange, and subtle magenta. The mark feels like abstract, liquid color geometry inside the black coin. Smooth boundaries and softly blended color transitions. No noisy texture, excessive surface detail, or illegible ornamentation. MATERIAL: Polished black polymer or ceramic outer body. Subtle metallic and glasslike response. Strong controlled specular reflection. Physical bevel highlights. Rich dark surface that never looks pure flat black. The center artwork is colorful and luminous but retains clear shape definition. ROTATION: Coins rotate along more than one axis. Use different angular velocities and phases for each instance. Their movements should reveal thickness and surface reflections. Avoid repetitive synchronized spinning. SECONDARY TOKEN SYSTEM Create a collection of distinct 3D liquid-staking token designs. Include recognizable variations of: Black SOL-marked token with colorful curved striped symbol. Purple and magenta glowing coins. Solana-inspired striped tokens. Yellow and orange branded coins. Cyan-and-white glowing symbol coins. Black-and-gold ring tokens. Smaller INF-style tokens. Each token must have: Real thickness. Individual material treatment. Physically coherent reflections. Distinct orientation. Independent rotation. Rim highlights. Controlled emissive or neon accents where appropriate. Appropriate front and side textures. Do not make every token identical except for the face image. PARTICLE SYSTEM Use a limited field of designed geometric accents. Types: Concave four-point sparkle forms. Bright lime-green diamond stars. Small orange and yellow quadrilaterals. Tiny violet and magenta specks. White glimmering star highlights. Distant miniature coins. Particles must vary in size, focus, distance, and movement. Foreground element
Details
0:24
OpenAIGPT-6 Astra
Rebuild my Codex setup around this tree. 1. Agents - scan ~/.codex/agents and .codex/agents for anything that already fits explorer, worker or researcher - draft TOML only for missing roles: explorer and researcher on gpt-6-luna, worker on gpt-6.1-sol, all at model_reasoning_effort medium - explorer and researcher get a read-only sandbox, only worker can write - skip agents pinned to another model and list them 2. Architect - add an architect on gpt-6-astra, model_reasoning_effort high, read-only sandbox - its only jobs: review plans, repeated errors and finished work - feed it the plan, the diff and the failing log, never the full transcript - force one output shape: verdict (proceed / revise / stop), top 3 risks, one cheaper path, under 200 words - cap it at 3 calls per task 3. Main config - in ~/.codex/config.toml set model to gpt-6.1-sol, model_reasoning_effort to high, approvals_reviewer to auto_review 4. Overrides - find anything that would beat this: active profiles, flags in shell aliases, agents.default_subagent_model - report it, change nothing 5. Rules - add to the AGENTS file in the repo root: spawn the architect before a large plan, when the same error signature shows up twice, and before calling a long task done - log every architect call with its trigger and verdict to .codex/architect-log.jsonl Check that every TOML file parses, then show me all changes as one diff. No edits until I say go.
Details
0:15
OpenAIGPT-6 Astra
make a dynamic 15 second motion graphics video that shows off your best work like it's a resume showreel, go all out
Details
Browse all GPT-6 Astra promptsExplore AI Video Prompts