Directing an AI Agent to Build a Full Site
Karthikeyan delegated the entire build of Cyberplain, a 32-article cybersecurity education site, to Hermes Agent. This approach involved the AI making design, content, and architectural decisions.…
Karthikeyan delegated the entire build of Cyberplain, a 32-article cybersecurity education site, to Hermes Agent. This approach involved the AI making design, content, and architectural decisions.
Karthikeyan, a developer new to cybersecurity, needed a full education site, Cyberplain, with 32 articles and interactive features. Instead of coding it himself, he tasked Hermes Agent with the entire build, providing only an idea and a reference site. This experiment, part of the Hermes Agent Challenge, aimed to test the limits of AI-directed development for a complex project.
The resulting site included a live security news feed from Hacker News and Reddit's r/netsec, an interactive knowledge graph with a custom spring-force physics simulation, and a secure newsletter form with a real-time subscriber count. The project demonstrates a shift in the founder's role from direct execution to strategic direction and oversight of an AI agent.
Delegating the Entire Build
Karthikeyan initiated the project by telling Hermes Agent, "You're in charge. Build it." The founder provided explainme.ai as a design inspiration but explicitly instructed the agent not to copy it. This broad directive meant the agent was responsible for design choices, content generation, architectural decisions, and deployment. The founder's role became one of initial setup and subsequent validation, rather than hands-on coding.
Content Generation at Scale
Hermes Agent generated all 32 articles for Cyberplain. The instruction focused on a "plain-language cybersecurity education site" with "no jargon. No hype." The agent developed a consistent "Sentinel's voice" for the content, described as explaining concepts clearly without performing expertise, distinct from a typical chatbot output. This allowed for rapid content production adhering to specific tonal and clarity requirements.
Architectural Decisions and Tooling
The agent made the core technology stack decisions: Astro for the framework, Tailwind for styling, and Vercel for hosting. This selection produced a static output site, complemented by a single serverless endpoint specifically for the newsletter subscription form. The agent also chose a dark-mode only design, using a GitHub-inspired palette (background: #0d1117, accent: #58a6ff), and implemented a grid layout for articles and specific typography. These decisions were made autonomously by the agent based on the initial project brief.
Debugging Critical Security Flaws
During development, a significant issue arose with the newsletter subscription form: the API key was hardcoded in client-side JavaScript. Karthikeyan flagged this vulnerability to Hermes Agent. The agent identified the problem, moved the API key server-side, and restructured the entire approach to secure the form. This demonstrated the agent's capacity to not only build but also to identify and rectify critical security flaws under direction, a task that often requires multiple refactors in traditional development.
Feature Implementation Beyond Content
Beyond the core articles, Hermes Agent implemented several complex features. It built a live security news feed by client-fetching data directly from Hacker News and Reddit's r/netsec. The agent also constructed an interactive knowledge graph, running on an HTML5 canvas, which included a custom spring-force physics simulation. Additionally, it developed a secure newsletter subscription form capable of delivering new articles twice weekly and displaying a live subscriber count badge in real time. These features highlight the agent's ability to integrate diverse functionalities into the site.
What We'd Change
While Karthikeyan's experience with Hermes Agent demonstrates the potential of AI-assisted development, certain aspects require scrutiny for broader applicability. The project was explicitly a submission for the "Hermes Agent Challenge," implying the primary goal was to showcase the agent's capabilities rather than optimize for commercial metrics like time-to-market or cost efficiency. This context means the "roughly zero time to build it myself" claim lacks quantitative backing regarding actual founder time spent directing and debugging.
The founder, despite being new to cybersecurity, possessed developer skills. A non-technical founder might struggle to identify critical issues like the client-side API key exposure or to provide sufficiently precise directives for complex features. The success here relies on a founder who can effectively communicate technical requirements and validate technical output. Furthermore, the complete delegation of "design, code, deployment, decisions" to a single AI agent, while efficient in this context, could limit strategic agility or introduce a single point of failure in a commercial product where human intuition and iterative feedback loops are crucial for market fit.
Landing
Karthikeyan's Cyberplain project illustrates a shift in the founder's operational paradigm. The emphasis moves from direct coding to strategic orchestration and validation of AI-driven development. This approach suggests that future product development may increasingly involve founders defining vision, setting guardrails, and auditing AI output, rather than executing every technical detail. The effectiveness of this model hinges on the founder's ability to articulate precise requirements and maintain vigilance over the AI's autonomous decisions, particularly in critical areas like security and user experience.
Pull quote: “”
Every claim ties to a primary source. See our methodology.