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

Memberships

Manychat Masterclass (Free)

2.2k members • Free

Ai Filmmaking

7k members • $7/month

AI Automation Society

381.7k members • Free

AI Automation Agency Hub

319.5k members • Free

HighLevel Systems Playbook

117 members • Free

AI Automation Agency Ninjas

20.8k members • Free

AI Automation (A-Z)

154.7k members • Free

Easy Machine AI

2k members • Free

Chase AI Community

65.9k members • Free

35 contributions to AI Automation Society
🚀New Video: 100 Hours Testing Claude Code vs ChatGPT Codex (honest results)
I spent 100 hours testing Claude Code vs ChatGPT Codex and what I found genuinely surprised me. Same prompts, same builds, both tools side by side, and one of them hit way harder than I expected. If you're picking between coding agents right now, then this video is the breakdown you actually need before you commit.
5 likes • 9h
@Ken Ashe I always use a variety of LLM's to perform sanity checks on each others output's. It is a handy practice and I am often surprised what they pick up when they cross check each other.
1 like • 2h
@Paulette Ng You should try it Paulette, as an example only, but if you create a Claude Code research paper ask CHAT GPT to review it or visa versa.
My setup for prompting AI agents
If you're building AI agents, I'd urge you to create a template for prompting. Two notable builds in the last month as proof: - I've built an AI agent that has handled over 9,000 emails - Another AI agent that's handling 25k customers. But here's the full setup: - A claude.md file that references a prompting guideline file, it tells Claude how to write prompts. - Once a prompt is approved, I write at the top "approved for production" which tells Claude that it should not make big changes. This makes sure that the prompt does not get destroyed by Claude. - Push the changes to my GitHub to keep track of all changes. This last part is where most people go wrong. When they see a mistake, they ask Claude to write an explicit rule to never do that again. The issue is that Claude will only look for that exact case, and if the next case doesn't match it, Claude will skip it. Instead, what I do is write mental models of the idea, what we're trying to do and why. When you do it this way, Claude has to use more reasoning to figure out which mental model makes sense. You're letting Claude think with some constraints. But this system has cut down my prompting time and also increased my reliability ten fold. And the thing is that I can use this wherever AI agents are used. Sales agent, customer service agent, any type of agent. Because the structure is the exact same every single time. Give me the agent and I'll make it reliable.
1 like • 4d
@Chris Jadama - I hear you although as you now you need to take steps. I use a lot of validate scripts to catch things from going astray. All API's only stored in System Environmental Variables. I also use dedicated skills for wrapping and eval of skills, scripts etc. I use dedicated local ports (proven clear and locked only for host work) e.g. 101** for main, 102** for preview and 103** for dev. Never any conflicts. e.g. localhost 10204 e.g. would be for dev version v1.4. The good thing about Mission Critical is that it greatly reduces hallucinations. Further, the rules are references which I can override at any point should I choose to.
0 likes • 2h
@Chris Jadama Get you LLM to do a port scan to identify all ports on your system. Feed the log back into the llm's so it always/s knows what ports are for what. The LLM then manages the port list e.g. (port-index.md) with the LLM help decide which to ports to dedicate to local host/s and lock it down with ai. Save it in claude.md / working-rules.md or just by a hook to either. ## Port Allocation Strategy Table Where: - **ENV_CODE** = 0 (Production) | 1 (Preview) | 2 (Development) - **MAJOR** = Major version number (e.g., 1 for v1.x) - **MINOR** = Minor version number (e.g., 5 for v1.5)
Defensive Hardening for AI Developers
When fellow members @David O'Donnell and @Brooks M shared information in this community about the “AI-Assisted Zero-Day 2FA Bypass Now in the Wild,” it prompted me to take a much closer look at my own security posture. I paused my planned work to conduct a security audit across my own architecture and ecosystem, and I am very glad I did. The process showed me that cybersecurity risks are far more complex, sophisticated, and easy to underestimate than many of us may realise. Like many developers, I had relied on standard operating system protections, VPNs, and a mix of paid or free security tools. A deeper review revealed multiple potential vulnerabilities and a much broader threat surface than I expected. I have since implemented emergency defensive hardening across 26 mechanisms and 9 distinct threat-category areas, including incident-response readiness. I have also attached my “Defensive Hardening for AI Developers” report for anyone who may find it useful. I am sharing this because I genuinely do not want any member here to become a cybersecurity victim. Please consider reviewing your own systems, especially if you handle client data, where the legal, financial, and reputational stakes are significantly higher. If you have any questions, please feel free to reach out. @Nate Herk , I hope it is okay for me to share this here. I do not want to interfere with the momentum of the group, but I believe this information is closely related and may be valuable to many members of the AIS community.
1 like • 4h
@Sean Murphy Your welcome
The skill clients pay $5000+ for (and it’s not automations)
I’ve been watching our 3,700 students in AIS+, and I noticed the people making the most money are all doing this: https://app.aiautomationsociety.ai/10-hours The people charging $5,000, $10,000, even $50,000 per engagement weren't better builders. Before they ever opened n8n/Claude Code, they did one thing differently: → They found the automations worth building first. It’s like a mini audit. Just by asking a few questions and mapping out the opportunities, they were able to get clients excited and also choose the right projects to work on. And the best part is you can practice by running this same system on YOURSELF. I call it 10 Hours to 10 Seconds, because doing this can easily save you or your clients 10 hours a week by automating the right things. Get all the details here: https://app.aiautomationsociety.ai/10-hours Talk soon, Nate PS: If you’re in AIS+, this has already been updated and provided to you at no cost. You can find it in the classroom
1 like • 9h
Thanks @Nate Herk - I'm in.
1 like • 8h
@Lucas Galdiano - @Adam Goad I would also like to know more about how did you get your first customers? in-person meetings or online?
What’s the weirdest niche you’ve built for?
Feels like every second post is med spas and real estate. Meanwhile I’m over here building stuff for: • Bike shops • Kids Book creators • Supplement brands • AI receptionists for fireplace companies Is it just me or is the real world random AF! 😂
1 like • 1d
@Bharath Kumar Well done Bharath. I would be to scared to read the transcripts of the s@#t that goes on in my mind. 🤣
1-10 of 35
Ric Bell
5
325points to level up
@ric-bell-2067
Hi, I'm Ric Bell — a self-taught builder from Sydney. Here to learn, share, and figure out how to turn what I'm building into something that pays.

Active 20m ago
Joined May 22, 2026
Powered by