<?xml version="1.0" encoding="UTF-8"?>
<!-- LeoTrace blog feed (RSS 2.0). Hand-maintained like the rest of the site:
     add an <item> at the top for every new post, newest first, and bump
     lastBuildDate. Linked from each blog and benchmark page's <head>. -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>LeoTrace blog</title>
    <link>https://leotrace.io/blog/</link>
    <atom:link href="https://leotrace.io/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Notes from LeoTrace on what AI coding agents get wrong about security, and on building LeoPrevent.</description>
    <language>en</language>
    <lastBuildDate>Mon, 26 Oct 2026 10:00:00 GMT</lastBuildDate>
    <item>
      <title>Coding agents copy your security mistakes</title>
      <link>https://leotrace.io/blog/coding-agents-copy-your-security-mistakes/</link>
      <guid isPermaLink="true">https://leotrace.io/blog/coding-agents-copy-your-security-mistakes/</guid>
      <pubDate>Mon, 26 Oct 2026 10:00:00 GMT</pubDate>
      <category>Benchmarks</category>
      <description>What two months of watching GPT-6 and Claude Opus 5.5 write code on flawed apps taught us, from interview challenges to real CVEs, and fixing a benchmark along the way.</description>
    </item>
    <item>
      <title>Hello, world</title>
      <link>https://leotrace.io/blog/hello-world/</link>
      <guid isPermaLink="true">https://leotrace.io/blog/hello-world/</guid>
      <pubDate>Mon, 26 Oct 2026 09:00:00 GMT</pubDate>
      <category>Company</category>
      <description>What this blog is for: what coding agents get wrong about security, building LeoPrevent, and how we measure whether it helps.</description>
    </item>
  </channel>
</rss>
