Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
Voice AI Academy

1k members • Free

Oleg's AI Lab

7.1k members • Free

Ai Bdarija

4.4k members • Free

AI First Lab - Le HUB

8.3k members • Free

AI Architect Academy

989 members • Free

AI Automation Society

439.1k members • Free

Communauté IA

73.9k members • Free

AI Accelerator

20k members • Free

AI Launchpad

33.9k members • Free

201 contributions to ARABIC AI AGENTS ACADEMY
Asking for opinions on my Codex workflow
Salam! This is a question for Codex / Claude Code users. I'd really appreciate your opinions and advice. Am I using Codex efficiently, or am I missing something? I'm not really stuck on the coding side. The project is progressing well, and Codex has been doing a pretty good job so far. What I'm questioning is whether I'm actually using it efficiently. For example, today Codex consumed around 60% of my weekly limit. It worked for almost 13 hours non-stop on a task I gave it at around 8 AM and only finished around 9 PM. So I feel like I might be consuming way too many tokens, or perhaps structuring my workflow in a way that makes Codex do more work than necessary. During this project, I've started learning about Skills and turning repetitive workflows into reusable skills. Right now I have: → List Upcoming Items : Loads bugs reported by testers and gives me a structured list of what needs to be worked on. → Explain Item : The application I'm working on is in Danish, which I don't speak. This skill translates the tester's report and explains what they found, what the actual bug is, and how it could potentially be fixed. → Tester : Simulates customer/artist replies and runs conversations through the application's AI so I can see how it responds. → Reviewer : Reads the entire resulting conversation and evaluates whether the AI handled it correctly or whether something still needs improvement. Few months ago, I discovered the idea of using an Orchestrator. I created one that combines these skills into a loop: Goal → Implement fix → Test → Review → Fix again if needed → Repeat until the reviewer considers the conversation good. Overall, the setup is working pretty well. But I still have this feeling that I'm missing something, or that I'm using Codex in a way that's much more expensive than it needs to be. 😅 So, for those of you who use Codex or Claude Code heavily: 1. Does this workflow make sense? 2. Are there better ways to structure the orchestrator/skills to reduce token usage and make Codex more efficient? 3. Are there any important Codex features, patterns, workflows, or best practices that I'm missing?
3 likes • 6d
Token consumption depends on the tokenization system. Some languages ​​are more "efficient" than others: English is generally one of the most optimized languages. Danish, Dutch, German, and French are relatively similar. Languages ​​with many special characters, ideograms, or complex grammatical forms may sometimes consume more tokens to express the same idea. For example, if a sentence requires: 100 tokens in English, it might require 105 to 120 tokens in Danish, or sometimes fewer depending on the wording. However, this is generally not a factor that significantly increases costs. The real causes of excessive token consumption are usually: very long prompts; a lot of context sent with each request; accumulated conversation histories; large JSON or data objects; loops of agents that re-query each other; RAG workflows injecting a lot of documents
Why Small Businesses Are Winning The AI Race With Agentic AI
Most businesses attempting to integrate AI are discovering the same thing: the technology is rarely the problem. The obstacle is the organization itself — the informal power structures, the processes people have built professional identities around, the quiet resistance to anything that redistributes how work and influence flows. The companies pulling furthest ahead are not transforming. They are building from scratch, and the results are beginning to appear in industries where nobody expected them. Source: https://www.forbes.com/sites/charlestowersclark/2026/06/23/why-small-businesses-are-winning-the-ai-race-with-agentic-ai/?ss=agentic-ai
5
0
Certificat Eduk8agentic.
🎓 Une nouvelle étape franchie dans mon parcours en Intelligence Artificielle Agentique. Je suis heureux de partager l’obtention de mon certificat de réussite du programme “Agentic AI Workflows Builder” avec Eduk8agentic. Cette formation m’a permis de renforcer mes compétences pratiques dans la conception, la construction et la mise en œuvre de systèmes d’IA agentique, capables de transformer des idées en workflows automatisés, fiables et opérationnels. Mais au-delà du certificat, je retiens surtout une expérience riche en apprentissage, en expérimentation et en construction concrète. Un grand merci à Zara Hunter, fondatrice d’Eduk8agentic, pour son expertise, son temps, sa disponibilité et surtout l’énergie et la passion investies tout au long de cette formation. Cette étape renforce une conviction : l’avenir ne consiste pas seulement à utiliser l’IA, mais à construire des systèmes capables d’agir, d’automatiser et de créer de la valeur. La suite ? Transformer ces compétences en solutions concrètes pour les entreprises et les PME, notamment à travers l’automatisation des processus et les workflows agentiques. Une certification obtenue. Beaucoup plus à construire. #AgenticAI #ArtificialIntelligence #AIWorkflows #Automation #AI #GenerativeAI #AIAgents #DigitalTransformation #Eduk8agentic #EasyDigia
Certificat Eduk8agentic.
2 likes • 10d
مبروك سي الزوهير
GITEX AI Türkiye
Türkiye has rapidly become one of the world's fastest-growing innovation ecosystems. Home to 114 technoparks, 12,800+ R&D companies, and 2,194 startups representing 16% of all startups in Eastern Europe, and ranked #38 globally in the 2026 Global Startup Ecosystem Index, the country is transforming breakthrough research into globally scalable businesses. This September, at GITEX Ai Türkiye, you'll have the opportunity to connect directly with technoparks across the country driving this momentum.
7
0
GITEX AI Türkiye
Vote on the learning schedule.
Salam Nous avons placé Blogging (AVO) en première position dans tous les choix pour deux raisons : @Na BeeLoud animera une réunion AVO la semaine prochaine, ce qui en fait naturellement notre première priorité. Ainsi, « Moudabir (Build & Sell) » désigne tout le travail après la sortie de la V1 : continuer à développer l'application, l'améliorer, la commercialiser, acquérir des utilisateurs et travailler dessus jusqu'à sa commercialisation et son évolution. Votre vote nous aidera à définir quelle sera la prochaine priorité après Blogging (AVO). We placed Blogging (AVO) first in every option for two reasons: @Na BeeLoud will be leading an AVO meeting next week, making it our natural first priority. Therefore, "Moudabir (Build & Sell)" refers to everything after the V1 release: continuing to develop the app, improve it, market it, acquire users, and keep working on it as we bring it to market and grow it. Your vote will help us decide what should be our next priority after Blogging (AVO).
Poll
15 members have voted
3 likes • 11d
AVO = Agentic Visibility Optimization
2 likes • 11d
Merci Hafsa
1-10 of 201
Omar B.
7
5,585 points to level up
@omar-bouizem-8655
Welcome to the new world

Active 2d ago
Joined Oct 6, 2025
Powered by