Skip to main content

Agrici Daniel

I build open-source AI marketing systems.

I like turning messy marketing work into tools people can inspect, test, and make their own.

I build it. I test it. I share it.

Agrici Daniel smiling in a studio portrait

Most of my projects start with a real problem I want to solve better. I turn the working parts into Claude Code skills, local workflows, and open-source tools for SEO, ads, content, research, and knowledge work.

I try to keep the process simple: show the source, keep the checks visible, say where the limits are, and leave real decisions with a person. If something works, I document it. If it breaks, I want that visible too.

I co-founded Rankenstein.pro, share practical walkthroughs on YouTube, and run AI Marketing Hub as a place for builders to ask questions, compare notes, and improve the systems together.

  • 44K+ GitHub stars
  • 50+ original public repositories
  • 5.2K Free Hub members
  • 280+ Pro builders

A few rules I keep

Show where it came from

I keep sources, observed facts, and assumptions separate. If I cannot explain where an answer came from, I do not treat it as ready.

Keep people in charge

I can move quickly on research, audits, and drafts. Publishing, spending, account changes, and other real actions still need a clear human yes.

Build in public, test in private

I share stable releases publicly. The Pro workshop is where we test rougher builds, debug together, and learn what should ship next.

One project led to another

  • 2024: I started turning practical SEO and marketing work into repeatable n8n and AI-assisted workflows.
  • 2025: I began releasing the useful parts on GitHub and built AI Marketing Hub for walkthroughs, questions, and field feedback.
  • 2026: The public portfolio grew to 44K+ GitHub stars, 50+ original public repositories, 5,200+ Free Hub members, and 280+ Pro builders.
  • Now: I keep stable releases public and use Pro as the faster workshop for live sessions, experiments, workflows, and support.

Speaking and building

A lot of my work happens quietly at a keyboard. Every now and then, I get to take the same build on stage, explain what I tried, and show the thing running.

I use what works

I use whatever makes the workflow clearer, easier to inspect, and easier to run again. If another tool does that better, I switch.

  • AI systems: Claude Code, OpenAI Codex, Gemini, and OpenAI
  • Marketing data: DataForSEO, Search Console, GA4, and PageSpeed Insights
  • Build layer: TypeScript, React, n8n, and GitHub

Pick what fits

  • Public tools - GitHub repositories, documentation, and project-specific licenses.
  • Free Hub - Release updates, questions, peer support, and public resources.
  • Pro workshop - Weekly sessions, private systems, recordings, and priority support.

Public facts last verified 2026-08-27. Current prices, access, and repository terms are controlled by their linked source pages.