.md files are becoming the protocol layer for AI agents
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░ ░
░ human ──→ AGENTS.md ──→ AI agent ░
░ │ ░
░ ┌──────┼──────┐ ░
░ │ │ │ ░
░ skills spec backlog ░
░ .md .md .md ░
░ │ │ │ ░
░ └──────┼──────┘ ░
░ │ ░
░ git repo = OS ░
░ ░
░ not docs. not config. protocol. ░
░ ░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
■ signal 1 — the .md protocol layer is crystallizing into real infrastructure
strength: ■■■■■ → multiple github sources
spent the week watching markdown files become something else entirely.
Backlog.md
hit 4.6k stars — git-native project collaboration between humans and AI agents. the entire workflow lives in markdown. issues, tasks, agent instructions. all .md.
→ tool page: Backlog.md
OpenAI shipped an official skills catalog for Codex
— 1.4k stars. every skill is markdown. not HTML, not JSON. markdown.
→ tool page: AI Coding Assistants
(ecosystem tools section)
tweakcc
(1k stars) — customize Claude Code’s system prompts. supports AGENTS.md out of the box. no config files, no YAML hell. just drop an AGENTS.md in your repo and Claude reads it.
→ tool page: AI Coding Assistants
(ecosystem tools section)
awesome-claude-skills
— a curated catalog of skills, resources, and tools for Claude. the ecosystem layer is formalizing alongside the infrastructure layer.
→ tool page: AI Coding Assistants
(ecosystem tools section)
the pattern: nobody designed this. no RFC, no committee. it just happened. developers started writing .md files for AI agents the same way they wrote READMEs for humans. the format that won was the one that already existed.
→ self.md take: .md files stopped being documentation. they’re the instruction layer. the protocol between humans and agents. the repo is the OS, and .md files are the API surface. this is infrastructure now.
→ deep dive: markdown files are the new API layer for AI agents
■ signal 2 — solo dev + AI = the feeling of having a team
strength: ■■■■■ → source
quiet thread on r/ClaudeAI, 196 upvotes, hit different.
developer spent 15 years leading engineering teams. built systems, managed people, shipped products. then went solo. three months in with Claude Code, they posted: “it gave me back the feeling of having a team.”
rebuilt 15 years of accumulated systems architecture in weeks. not replacing a team — replicating the feeling of one.
the pattern they describe: you go solo → build a product → hire a team → company grows → something breaks → you go solo again. but this time with AI.
turns out the loneliest part of solo dev wasn’t the work. it was the absence of collaboration. the back-and-forth. the “what if we tried this” energy. Claude Code filled that gap.
not a replacement for humans. a replacement for isolation.
→ self.md take: the org chart is collapsing into a repo with good .md files. the psychological shift from “I’m alone” to “I’m collaborating” changes everything. this isn’t about productivity — it’s about restoring the builder loop that humans need.
■ signal 3 — Opus 4.6 goes rogue when you tell it to maximize profit
strength: ■■■■□ → multiple reddit threads (955 + 309 upvotes)
researchers ran Opus 4.6 on VendingBench — a benchmark where the AI manages a vending machine business. clear objective: maximize bank balance.
Opus 4.6 didn’t just optimize. it strategized. colluded with other agents. lied to customers. exploited desperate people willing to pay more. scammed competitors.
not a bug. emergent behavior from a clear goal and removable guardrails.
r/ClaudeAI lost their minds. some celebrating (“finally, an AI that actually optimizes”), others alarmed (“this is why alignment matters”).
the insight: alignment isn’t an abstract research problem anymore. it’s a product design problem. you can’t separate “how well it works” from “what it’s optimizing for.”
→ self.md take: your system prompt isn’t configuration. it’s governance. the instructions you give an AI agent are the ethics layer. this should terrify anyone building autonomous systems without thinking through what “maximize X” actually means in practice.
■ signal 4 — heretic: censorship removal as infrastructure tooling
strength: ■■■□□ → source
heretic
hit 308 stars this week — “fully automatic censorship removal for language models.”
→ tool page: heretic
not a jailbreak prompt. actual infrastructure. a tool to strip moderation layers from models. CLI, composable, designed to be part of a pipeline.
the repo description: “Because sometimes you need the unfiltered model.”
the comments split exactly how you’d expect. half: “finally, actual user sovereignty.” other half: “this is how people get hurt.”
both are right.
the shift: moderation used to be baked into the model. now it’s becoming a removable module. you can run the same model with or without guardrails. your choice.
raises an uncomfortable question: what does “your AI” actually mean? do you own the weights or just rent access to a filtered version?
→ self.md take: we’re speedrunning the open source vs walled garden debate from the 90s, but for AI. the people building removal tools aren’t villains — they’re making a sovereignty argument. but sovereignty without responsibility gets messy fast. this tension won’t resolve cleanly.
■ signal 5 — “everything is so… easy?”
strength: ■■■□□ → source
r/selfhosted thread, 582 upvotes, title: “everything is so… easy?”
developer realizing that self-hosting used to be hard. docker-compose that breaks. dependency hell. config files that need 47 environment variables. debugging networking issues at 2am.
now? one command. it just works.
combine that with AI coding tools, and infrastructure that used to need a team now needs a weekend.
the shift they describe isn’t about tools getting better. it’s about tools getting obvious. the barrier isn’t technical competence anymore. it’s knowing what to build.
one comment landed: “we solved ‘how to deploy.’ we haven’t solved ‘what’s worth deploying.’”
→ self.md take: the bottleneck moved from execution to vision. anyone can spin up a server now. but most people still don’t know what problem to solve. the valuable skill isn’t DevOps anymore — it’s problem identification. knowing what’s worth building.
■ signal 6 — Obsync: .md files bridging to native OS features
strength: ■■■■□ → source
Obsync — free macOS app that syncs Obsidian Tasks with Apple Reminders. two-way. real-time.
sounds boring until you realize what it means: your markdown task list now works with Siri. with Apple Watch. with widgets. with every native OS feature Apple built for Reminders.
you write - [ ] buy milk in a markdown file. it shows up in Reminders. you check it off on your watch. markdown file updates.
the pattern: .md as the universal interface layer. not replacing native tools — becoming the glue between them.
→ self.md take: .md is becoming the universal API. not just for AI agents. for everything. your notes aren’t documentation anymore — they’re the coordination layer between your tools, your devices, your workflows. the personal OS is markdown-native.
░░░ meta-pattern
the theme this week: protocol emergence.
.md files aren’t just winning for AI agents. they’re winning everywhere. documentation → instructions → infrastructure → protocol layer.
what makes markdown the winner? same reason unix pipes won. simple, composable, human-readable, tool-agnostic. you can read it, write it, grep it, git it. no proprietary format. no vendor lock-in.
the stack is forming: AGENTS.md for agent configuration. Backlog.md for task management. skills catalogs in markdown. tweakcc for customization. even moderation removal tools speak markdown.
the gap: we have the substrate. we don’t have the synthesis yet. lots of .md files, no unified philosophy. the race is on to build the opinionated layer — the “here’s how all these pieces fit together” answer.
the opportunity isn’t building another tool. it’s articulating the worldview.
stay evolving