Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add davekilleen/Dex --skill agent-native-architecturegit clone --depth 1 https://github.com/davekilleen/DexWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/davekilleen/dex/agent-native-architecture)<a href="https://agentmods.dev/skills/davekilleen/dex/agent-native-architecture"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/agent-native-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/davekilleen/dex/agent-native-architecture"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/agent-native-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00047 | $0.05045 |
| Opus 5.5 | $0.00019 | $0.02018 |
| Sonnet 5.5 | $0.00009 | $0.01009 |
| Haiku 4.5 | $0.00005 | $0.00505 |
Grade A, and why
agent-native-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
Copies of this mod
6 near-identical copies found in the catalogue:
- agent-native-architecture — 100% identical, 0 lines differ
- agent-native-architecture — 100% identical, 0 lines differ
- agent-native-architecture — 94% identical, 16 lines differ
- agent-native-architecture — 92% identical, 55 lines differ
- agent-native-architecture — 92% identical, 18 lines differ
- agent-native-architecture — 89% identical, 64 lines differ
How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<why_now>
Why Now
Software agents work reliably now. Claude Code demonstrated that an LLM with access to bash and file tools, operating in a loop until an objective is achieved, can accomplish complex multi-step tasks autonomously.
The surprising discovery: a really good coding agent is actually a really good general-purpose agent. The same architecture that lets Claude Code refactor a codebase can let an agent organize your files, manage your reading list, or automate your workflows.
The Claude Code SDK makes this accessible. You can build applications where features aren't code you write—they're outcomes you describe, achieved by an agent with tools, operating in a loop until the outcome is reached.
This opens up a new field: software that works the way Claude Code works, applied to categories far beyond coding. </why_now>
<core_principles>
Core Principles
1. Parity
Whatever the user can do through the UI, the agent should be able to achieve through tools.
This is the foundational principle. Without it, nothing else matters.
Imagine you build a notes app with a beautiful interface for creating, organizing, and tagging notes. A user asks the agent: "Create a note summarizing my meeting and tag it as urgent."
If you built UI for creating notes but no agent capability to do the same, the agent is stuck. It might apologize or ask clarifying questions, but it can't help—even though the action is trivial for a human using the interface.
The fix: Ensure the agent has tools (or combinations of tools) that can accomplish anything the UI can do.
This isn't about creating a 1:1 mapping of UI buttons to tools. It's about ensuring the agent can achieve the same outcomes. Sometimes that's a single tool (create_note). Sometimes it's composing primitives (write_file to a notes directory with proper formatting).
The discipline: When adding any UI capability, ask: can the agent achieve this outcome? If not, add the necessary tools or primitives.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/action-parity-discipline.md 11 KB
- references/agent-execution-patterns.md 13 KB
- references/agent-native-testing.md 16 KB
- references/architecture-patterns.md 17 KB
- references/dynamic-context-injection.md 9.4 KB
- references/files-universal-interface.md 9.9 KB
- references/from-primitives-to-domain-tools.md 12 KB
- references/mcp-tool-design.md 15 KB
- references/mobile-patterns.md 25 KB
- references/product-implications.md 13 KB
- references/refactoring-to-prompt-native.md 8.4 KB
- references/self-modification.md 7.7 KB
- references/shared-workspace-architecture.md 20 KB
- references/system-prompt-design.md 6.4 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 436 lines · 47 tokens per session scan A 7913515b9404
agent-native-architecture is a skill published in the GitHub repository davekilleen/Dex (512 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 5,045 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
agent-native-architecture compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| agent-native-architecturedavekilleen/Dex | Skill | 512 | 8d ago | MIT | A | 47 | Claude Code |
| nft-standardswshobson/agents | Skill | 42k | yesterday | MIT | A | 48 | Claude Code |
| istio-traffic-managementwshobson/agents | Skill | 42k | yesterday | MIT | A | 40 | Claude Code |
| projection-patternswshobson/agents | Skill | 42k | yesterday | MIT | A | 36 | Claude Code |
| 9router-web-searchdecolua/9router | Skill | 32k | 9d ago | MIT | A | 74 | Claude Code, Codex |
| microservices-patternswshobson/agents | Skill | 42k | yesterday | MIT | A | 38 | Claude Code |
| track-managementwshobson/agents | Skill | 42k | yesterday | MIT | A | 44 | Claude Code |