Avid's banner
Avid's profile picture

Avid

@Av1dlive • 30,545 subscribers

i write,read and build/i normie-maxx /founder of agentic-stack (2.9k ⭐ on GitHub) / building https://t.co/lPuWxlhYsX (1023 downloads) / OSS Ambassador @evermind

Shorts

THIS IS HOW FABLE 5 MOVES WHEN YOUR VAULT IS BUILT RIGHT direct path. zero wandering. hits the target on the first try. without structure it's the opposite. 7 files opened. 2 minutes wasted. brief from 3 months ago still missing. one index file per major folder. gives the agent a direct line to what it needs. same task dropped from 2 minutes to 10 seconds. same model. nothing else changed. build the path or watch it search in the dark. full breakdown in the article below ↓

THIS IS HOW FABLE 5 MOVES WHEN YOUR VAULT IS BUILT RIGHT direct path. zero wandering. hits the target on the first try. without structure it's the opposite. 7 files opened. 2 minutes wasted. brief from 3 months ago still missing. one index file per major folder. gives the agent a direct line to what it needs. same task dropped from 2 minutes to 10 seconds. same model. nothing else changed. build the path or watch it search in the dark. full breakdown in the article below ↓

910,117 views

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this👇] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.

jev + sonnet 5.5 is f**king insane. my entire workflow got 4x faster after adding these 6 lines to CLAUDE.md. [with jev connected, paste this👇] 1. Before you start a Claude worker, ask Jev once to select a host-approved profile with one or two sessions. The profile must specify each session’s model and effort level. If Jev makes no selection, use the host default. 2. The host must check Jev’s selection. The host must set the model and effort before each session starts. Keep these settings fixed during the session. The host controls permissions and approvals. 3. Use Sonnet 5.5 at medium effort for clear coding tasks. Use higher effort for complex reasoning or JSON tasks. Use a second Claude only for independent research or a review that the user requested. 4. Give the second Claude the task, applicable files, limits, and completion requirements. Return its findings and evidence to the lead. 5. Complete the requested work. Ask the user only when you cannot continue without input or before an action that needs approval. Do not add features, tests, files, documentation, refactors, or review rounds that the user did not request. When the work is complete and checked, stop. Report the result. 6. Before you report completion, run a test, build, type check, or command that checks the code change. If no check can run, identify the missing check. Explain why it cannot run. same task. two timers. watch the difference.

177,825 views

people are building $100M company using 0 humans not even a single human. we are fully replaced here's how > they will use paperclip >allows to create org charts by spawning subagents >works with Claude Code, codex and even cursor the future is fully agentic companies. most people will bookmark and leave. don't be them^^

people are building $100M company using 0 humans not even a single human. we are fully replaced here's how > they will use paperclip >allows to create org charts by spawning subagents >works with Claude Code, codex and even cursor the future is fully agentic companies. most people will bookmark and leave. don't be them^^

550,089 views

this is the next $100B opportunity in ai , most will miss it's harness engineering what this agentic engineer reveals is insane >The model is almost irrelevant. The harness is everything >every failure is a signal about what the environment needs. >when agent throughput far exceeds human attention, corrections are cheap and waiting is expensive most people will ignore and bookmark. be different.

this is the next $100B opportunity in ai , most will miss it's harness engineering what this agentic engineer reveals is insane >The model is almost irrelevant. The harness is everything >every failure is a signal about what the environment needs. >when agent throughput far exceeds human attention, corrections are cheap and waiting is expensive most people will ignore and bookmark. be different.

497,726 views

holy sh*t this is f**king dangerous i just figured out how to run Opencode in Codex It has Deepseek V4 Flash which replaces Opus 5 at 1/4th price You can get 10,000 request in only $10/month along with Kimi K3 and Qwen 3.5 Max [here is how you set it up] 1. install the 'codex-router' 2. Put in the Opencode Go API key 3. Done that's it Save this no matter what. This will be the best thing you do this week

holy sh*t this is f**king dangerous i just figured out how to run Opencode in Codex It has Deepseek V4 Flash which replaces Opus 5 at 1/4th price You can get 10,000 request in only $10/month along with Kimi K3 and Qwen 3.5 Max [here is how you set it up] 1. install the 'codex-router' 2. Put in the Opencode Go API key 3. Done that's it Save this no matter what. This will be the best thing you do this week

131,503 views

life when you understand how to win like elon musk you start using game theory and constructing your own reality

life when you understand how to win like elon musk you start using game theory and constructing your own reality

219,592 views

this is literally f**king insane i just 2x my usage limits on $200/mo codex i figured out how to use deepseek v4.1-flash on $10/mo opencode go for routine subagent work... while gpt-6 astra directs the project and sol handles implementation. here's how to set it up in 3 mins: → connect opencode go to codex through model-router → install quota flow, including its skill and agent profiles → open a fresh astra task and paste: quota flow tells flash to handle discovery and checks, sol to implement, and luna to review when needed. the same implementation agent keeps its context through the build → test → fix loop. every extra agent should earn its call.

this is literally f**king insane i just 2x my usage limits on $200/mo codex i figured out how to use deepseek v4.1-flash on $10/mo opencode go for routine subagent work... while gpt-6 astra directs the project and sol handles implementation. here's how to set it up in 3 mins: → connect opencode go to codex through model-router → install quota flow, including its skill and agent profiles → open a fresh astra task and paste: quota flow tells flash to handle discovery and checks, sol to implement, and luna to review when needed. the same implementation agent keeps its context through the build → test → fix loop. every extra agent should earn its call.

63,870 views

this is f**king insane someone figured out how to use fable 5.1 with free gpt 5.6 luna subagents and never hit usage limits [here is how to set it up in 3 mins] 1. install 'fable-orchestrator' repo 2. type /fable [task] 3. done save this and give it to your agent

this is f**king insane someone figured out how to use fable 5.1 with free gpt 5.6 luna subagents and never hit usage limits [here is how to set it up in 3 mins] 1. install 'fable-orchestrator' repo 2. type /fable [task] 3. done save this and give it to your agent

67,182 views

codex usage got f**king nerfed. so i'm switching from gpt-5.6 sol (max) to mimo-v2.6-pro on opencode... it matches the performance for 1/10th price and almost 2x speed [here is how to set it up in codex in 1 min] 1. model-router → model-picker → toggle the... 2. Cmd+Q Codex 3. ready to go

codex usage got f**king nerfed. so i'm switching from gpt-5.6 sol (max) to mimo-v2.6-pro on opencode... it matches the performance for 1/10th price and almost 2x speed [here is how to set it up in codex in 1 min] 1. model-router → model-picker → toggle the... 2. Cmd+Q Codex 3. ready to go

34,982 views

this is the best trick to maximum usage limits on chatgpt codex codex's best kept secret is that your main agent doesn't have to do everything... custom agents are just files in ~/.codex/agents, and one file gives you a second worker on deepseek v4 flash > create ~/.codex/agents/deepseek-worker.toml > set model = "opencode-go/deepseek-v4-flash" with model_reasoning_effort = "max" > keep it bounded: one task packet, no scope creep, report back ```toml name = "deepseek_worker" description = "bounded implementation, testing, and cleanup on deepseek v4 flash" model = "opencode-go/deepseek-v4-flash" model_reasoning_effort = "max" ``` then @ deepseek_worker in the composer... your root agent plans while the worker ships the implementation planning on the main model, execution on the flash lane... that's the whole trick (we run this exact file, last i checked it keeps the heavy turns off the main thread)

this is the best trick to maximum usage limits on chatgpt codex codex's best kept secret is that your main agent doesn't have to do everything... custom agents are just files in ~/.codex/agents, and one file gives you a second worker on deepseek v4 flash > create ~/.codex/agents/deepseek-worker.toml > set model = "opencode-go/deepseek-v4-flash" with model_reasoning_effort = "max" > keep it bounded: one task packet, no scope creep, report back ```toml name = "deepseek_worker" description = "bounded implementation, testing, and cleanup on deepseek v4 flash" model = "opencode-go/deepseek-v4-flash" model_reasoning_effort = "max" ``` then @ deepseek_worker in the composer... your root agent plans while the worker ships the implementation planning on the main model, execution on the flash lane... that's the whole trick (we run this exact file, last i checked it keeps the heavy turns off the main thread)

50,262 views

Codex users, do this now for Astra: give it a nightly job to clean up its own instructions. your AGENTS.md and Skills might still be telling it to read irrelevant docs, repeat checks, and ask permission for tiny edits... i scheduled mine for 2am ET: → audit broad Skill triggers and conflicting rules → apply small fixes with backups and verification → keep safety boundaries, necessary tests, and approvals for sensitive actions unchanged files get skipped. meaningful changes come back with a diff. [copy this into Codex:] “Create a nightly automation at 2am to audit my personal AGENTS.md and locally maintained Skills. Identify unnecessary reading, broad triggers, redundant checks, and conflicting instructions. Apply minimal fixes, preserve safeguards and required tests, back up originals, and verify changes. Exclude vendor-managed files. Skip unchanged files. Notify me only about meaningful changes or blockers.”

Codex users, do this now for Astra: give it a nightly job to clean up its own instructions. your AGENTS.md and Skills might still be telling it to read irrelevant docs, repeat checks, and ask permission for tiny edits... i scheduled mine for 2am ET: → audit broad Skill triggers and conflicting rules → apply small fixes with backups and verification → keep safety boundaries, necessary tests, and approvals for sensitive actions unchanged files get skipped. meaningful changes come back with a diff. [copy this into Codex:] “Create a nightly automation at 2am to audit my personal AGENTS.md and locally maintained Skills. Identify unnecessary reading, broad triggers, redundant checks, and conflicting instructions. Apply minimal fixes, preserve safeguards and required tests, back up originals, and verify changes. Exclude vendor-managed files. Skip unchanged files. Notify me only about meaningful changes or blockers.”

35,516 views

Holy sh*t, this is f**king insane. Someone figured out how to make Claude sound like a Human instead of AI slop. Add this to your Claude.md. [here is how in 2 mins] 1. Open Claude > Settings > General > Instructions for Claude 2. Paste "anti-slop" prompt 3. you are done

Holy sh*t, this is f**king insane. Someone figured out how to make Claude sound like a Human instead of AI slop. Add this to your Claude.md. [here is how in 2 mins] 1. Open Claude > Settings > General > Instructions for Claude 2. Paste "anti-slop" prompt 3. you are done

39,482 views

grok bot + obsidian is basically superhuman mode... my agent team now has a second brain... a karpathy-style llm wiki for every bot, every decision, and every piece of research. p.s. this video was made and edited by grok bot in cap (here’s how i set it up in roughly 5 minutes) 1/ create one obsidian vault on the chief of staff’s computer. make Home.md the door. 2/ create Hunt folders for twitter, github, hacker-news, reddit, product-hunt, and inbox. 3/ create Ship folders for drafts, digests, angles, and builds. 4/ create the CoS wiki: Index, How-it-works, Today, and Decisions. 5/ create Maps for Jarvis, Hooks, and TELOS. 6/ use graph colors: gold for wiki, teal for maps, blue for twitter, green for github. 7/ file first. every note gets a date and a folder. 8/ scouts write into Hunt and never ping you. chat only receives a short digest. 9/ nothing in the vault posts, pays, or sends. the final yes stays human. 10/ run the daily loop: 08:00 IST for the Daily note, then agency reports at 08:14, 14:14, and 20:14. 11/ performance writes to twitter/live-score. staff engineer writes to builds/. 12/ lock decisions in Wiki/Decisions so dead posts don’t get remade. 13/ earn hooks in Maps/Hooks: trend -> foil -> hook family -> artifact -> lock. don't waste time reading this. give it to your agent

grok bot + obsidian is basically superhuman mode... my agent team now has a second brain... a karpathy-style llm wiki for every bot, every decision, and every piece of research. p.s. this video was made and edited by grok bot in cap (here’s how i set it up in roughly 5 minutes) 1/ create one obsidian vault on the chief of staff’s computer. make Home.md the door. 2/ create Hunt folders for twitter, github, hacker-news, reddit, product-hunt, and inbox. 3/ create Ship folders for drafts, digests, angles, and builds. 4/ create the CoS wiki: Index, How-it-works, Today, and Decisions. 5/ create Maps for Jarvis, Hooks, and TELOS. 6/ use graph colors: gold for wiki, teal for maps, blue for twitter, green for github. 7/ file first. every note gets a date and a folder. 8/ scouts write into Hunt and never ping you. chat only receives a short digest. 9/ nothing in the vault posts, pays, or sends. the final yes stays human. 10/ run the daily loop: 08:00 IST for the Daily note, then agency reports at 08:14, 14:14, and 20:14. 11/ performance writes to twitter/live-score. staff engineer writes to builds/. 12/ lock decisions in Wiki/Decisions so dead posts don’t get remade. 13/ earn hooks in Maps/Hooks: trend -> foil -> hook family -> artifact -> lock. don't waste time reading this. give it to your agent

17,154 views

grok bot + grok 4.6 can literally build any idea from 0 to 100 [here is the exact grok bot setup that does that] 1. extract all your claude code and codex sessions to your chief of staff. it will help structure the team 2. give it an auth.md for credentials and paste the video below to make the entire team

grok bot + grok 4.6 can literally build any idea from 0 to 100 [here is the exact grok bot setup that does that] 1. extract all your claude code and codex sessions to your chief of staff. it will help structure the team 2. give it an auth.md for credentials and paste the video below to make the entire team

10,949 views

Videos

Av1dlive's profile picture

the highest alpha play right now is so simple most people will never do it... make a harness that works for YOU it'll 10x the quality and speed of your AI outputs. paste this ONE prompt into your agent: ---------start of the prompt---------------- Build me a Langfuse-style observability dashboard from my own AI coding sessions for the last 7 days. SOURCES (read locally, read-only): - Claude Code: ~/.claude/projects/**/*.jsonl - Codex: ~/.codex/sessions/**/*.jsonl (and ~/.codex/history.jsonl) Never print secrets, keys or full prompt text. Snippets max 10 words, with keys, paths, URLs and long ids stripped. STEP 1. Write a stdlib-only Python script that computes, per tool: - sessions per day, user prompts, tool calls by tool name, failed tool calls by tool and error type - models used, tokens (input, output, cache read/write) per model per day - tool-call latency p50/p95, overall and per tool; session length p50/p95 - top sessions by tokens, longest sessions, retries (same tool call repeated after an error) - prompts clustered into task types (build, debug, deploy, research, writing, UI, review, other) - sessions grouped by project (working directory), with subagent runs flagged If a log doesn't record something, write "not logged". Never invent numbers. Save the result as harness-summary.json. STEP 2. Render a single-file dashboard.html (dark, animated numbers and charts): - Summary strip: total tool calls, prompts, error rate, tokens, p95 latency - Traces table: one row per session (tool, project, start, duration, prompts, tool calls, errors, tokens, model); search, filter by tool, sort, toggle to hide subagent runs - Trace detail: click a session to see a waterfall of its turns and tool calls with ok/error and duration - Sessions by project, tokens over time by model, a model table (tokens, error rate) - Latency view per tool, and an error explorer grouped by tool and error type - Heuristic scores (tool success rate, retries, per-session health), clearly labeled "heuristic" Cap embedded traces at the top 200 sessions by tokens if the file gets too big. STEP 3. From the data, write HARNESS.md proposing changes to CLAUDE.md / AGENTS.md: - Model routing: which model for which task type, based on what I used and what failed - Tools: keep (high use, low failure), fix (high failure), cut (rarely used) - Skills: one for every task type I repeated 3+ times, with a trigger line and steps - Guardrails: my top 3 failure patterns and a check that prevents each - Budget: my top 5 token sinks and one change that would cut each Cite the sessions behind each suggestion. STEP 4. Show me the 5 headline numbers and the proposed diff before changing any config. I'll review weekly and change only what the data shows. --------end of the prompt-------------

Avid

48,308 views • 19 days ago