<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://antaoalmada.dev/</id><title>Antão Almada</title><subtitle>Exploring the architecture, governance, and craft of AI coding agents — from agent design patterns and skills to observability and supply-chain risks. With a side of high-performance .NET for good measure.</subtitle> <updated>2026-07-19T00:02:15+01:00</updated> <author> <name>Antão Almada</name> <uri>https://antaoalmada.dev/</uri> </author><link rel="self" type="application/atom+xml" href="https://antaoalmada.dev/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://antaoalmada.dev/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Antão Almada </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>OpenWiki and OKF: Agent-Readable Code Wikis</title><link href="https://antaoalmada.dev/posts/OpenWiki-and-OKF-Agent-Wikis/" rel="alternate" type="text/html" title="OpenWiki and OKF: Agent-Readable Code Wikis" /><published>2026-07-18T00:00:00+01:00</published> <updated>2026-07-18T00:00:00+01:00</updated> <id>https://antaoalmada.dev/posts/OpenWiki-and-OKF-Agent-Wikis/</id> <content type="text/html" src="https://antaoalmada.dev/posts/OpenWiki-and-OKF-Agent-Wikis/" /> <author> <name>Antão Almada</name> </author> <category term="ai" /> <summary>Documenting a codebase has always been hard. Writing good documentation takes time, and keeping it current as the code evolves takes discipline that most teams cannot consistently sustain. The result is the familiar pattern: documentation that starts accurate, drifts, contradicts the code, and eventually gets ignored altogether. Coding agents change this. An agent can read source files, infer ...</summary> </entry> <entry><title>Knowledge Graph Tools for AI Code Agents</title><link href="https://antaoalmada.dev/posts/Code-Agent-Knowledge-Graphs/" rel="alternate" type="text/html" title="Knowledge Graph Tools for AI Code Agents" /><published>2026-07-03T00:00:00+01:00</published> <updated>2026-07-12T16:04:01+01:00</updated> <id>https://antaoalmada.dev/posts/Code-Agent-Knowledge-Graphs/</id> <content type="text/html" src="https://antaoalmada.dev/posts/Code-Agent-Knowledge-Graphs/" /> <author> <name>Antão Almada</name> </author> <category term="ai" /> <summary>Letting an agent grep your codebase from scratch every session is expensive and error-prone. Knowledge graph tools pre-build a navigable semantic index — functions, call graphs, types, dependencies — that agents query at near-zero cost per request. This post compares Graphify, GitNexus, codebase-memory-mcp, and CodeGraph: what each builds, how it exposes queries, and which fits your workflow. ...</summary> </entry> <entry><title>From Hero Prompts to Shared AI Infrastructure</title><link href="https://antaoalmada.dev/posts/From-Hero-Prompts-to-Shared-AI-Infrastructure/" rel="alternate" type="text/html" title="From Hero Prompts to Shared AI Infrastructure" /><published>2026-06-29T00:00:00+01:00</published> <updated>2026-07-12T16:04:01+01:00</updated> <id>https://antaoalmada.dev/posts/From-Hero-Prompts-to-Shared-AI-Infrastructure/</id> <content type="text/html" src="https://antaoalmada.dev/posts/From-Hero-Prompts-to-Shared-AI-Infrastructure/" /> <author> <name>Antão Almada</name> </author> <category term="ai" /> <summary>A hero prompt is the long, carefully tuned instruction one developer writes to make an agent behave well — once. If that knowledge lives only in one person’s head, the team has built a dependency, not infrastructure. This post argues that the useful parts of AI workflows need to be explicit, versioned, and committed with the repository, and shows how instructions, hooks, and custom agents make ...</summary> </entry> <entry><title>Prompt Caching for Coding Agents Explained</title><link href="https://antaoalmada.dev/posts/Prompt-Caching-for-Coding-Agents/" rel="alternate" type="text/html" title="Prompt Caching for Coding Agents Explained" /><published>2026-06-27T00:00:00+01:00</published> <updated>2026-07-12T16:04:01+01:00</updated> <id>https://antaoalmada.dev/posts/Prompt-Caching-for-Coding-Agents/</id> <content type="text/html" src="https://antaoalmada.dev/posts/Prompt-Caching-for-Coding-Agents/" /> <author> <name>Antão Almada</name> </author> <category term="ai" /> <summary>Usage-based billing changed the economics of coding agents. It is no longer enough to ask whether an agent can solve a task. We also need to ask how many tokens it burns while doing it. In Reducing Token Usage in Code Agents, the focus was context engineering: reduce noise, retrieve less, send better inputs. This post covers the other major lever: prompt caching — what it is, how it works, and...</summary> </entry> <entry><title>Profiling Coding Agents with /troubleshoot</title><link href="https://antaoalmada.dev/posts/Profiling-Coding-Agents-with-Troubleshoot/" rel="alternate" type="text/html" title="Profiling Coding Agents with /troubleshoot" /><published>2026-06-24T00:00:00+01:00</published> <updated>2026-07-12T16:04:01+01:00</updated> <id>https://antaoalmada.dev/posts/Profiling-Coding-Agents-with-Troubleshoot/</id> <content type="text/html" src="https://antaoalmada.dev/posts/Profiling-Coding-Agents-with-Troubleshoot/" /> <author> <name>Antão Almada</name> </author> <category term="ai" /> <summary>Every coding agent session has a cost — tokens burned, tools called, retries attempted. GitHub Copilot’s /troubleshoot command turns opaque agent logs into a readable profile: where tokens went, which tool calls failed, and what changes will make the next run cheaper. This post shows how to use it as a profiler for agent sessions. Coding agents make this problem more interesting. They produce ...</summary> </entry> </feed>
