amplifier-philosophy skillA
amplifier-philosophy is agent-read markdown (skill) from microsoft/amplifier-bundle-skills: Amplifier design philosophy using Linux kernel metaphor. Covers mechanism vs policy, module architecture, event-driven design, and kernel principles. Use when designing new modules or making architectural decisions..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Amplifier Philosophy: The Linux Kernel Metaphor
## Core Principle: Mechanism Not Policy
**If two teams might want different behavior, it belongs in a module, not the kernel.**
The kernel provides mechanisms (mount, emit, dispatch). Modules provide policies (what to mount, when to emit, how to handle).
## Architecture Patterns
### Kernel (amplifier-core)
**Keep it minimal and stable:**
- Session management (`session_create`, `mount`, `unmount`)
- Event emission (`emit`)
- Hook registration
- Context access
**Never add to kernel:**
- Provider selection
- Tool routing
- Plan generation
- Default behaviors
- File I/O
### Modules (Everything Else)
**All capabilities as modules:**
- **Providers**: LLM backends (Anthropic, OpenAI, Ollama)
- **Tools**: Capabilities (filesystem, bash, web)
- **Orchestrators**: Execution strategies
- **Context Managers**: State management
- **Hooks**: Lifecycle observers
## Mount Point System
Think of modules as **devices mounted at paths**:
```
/mnt/providers/{name} - LLM backends
/mnt/tools/{name} - Agent capabilities
/mnt/hooks/{event} - Lifecycle observers
/mnt/context - Conversation state
…Read the whole file at its exact version.
How to install
mdr add microsoft/amplifier-bundle-skills/amplifier-philosophy@v1.0.0mdr add microsoft/amplifier-bundle-skills/amplifier-philosophy@sha256:3c2e3011ccd44a31Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_zos77lytyjgaunqu)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3183 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
microsoft/amplifier-bundle-skills · 12 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zos77lytyjgaunqu GET https://markdownregistry.com/api/v1/resolve?ref=microsoft/amplifier-bundle-skills/amplifier-philosophy GET https://markdownregistry.com/api/v1/blob/3c2e3011ccd44a31fc10917a4a78eef4639f3653370f3c801896951fd661cd1e
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.