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 athola/claude-night-market --skill architecture-paradigm-microkernelgit clone --depth 1 https://github.com/athola/claude-night-marketWrote 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/athola/claude-night-market/architecture-paradigm-microkernel)<a href="https://agentmods.dev/skills/athola/claude-night-market/architecture-paradigm-microkernel"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigm-microkernel/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/athola/claude-night-market/architecture-paradigm-microkernel"><img src="https://agentmods.dev/badge/skills/athola/claude-night-market/architecture-paradigm-microkernel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00867 |
| Opus 5.5 | $0.00013 | $0.00347 |
| Sonnet 5.5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
architecture-paradigm-microkernel 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Microkernel (Plugin) Architecture Paradigm
When To Use
- Building extensible systems with plugin architectures
- Products requiring customer-specific customizations
When NOT To Use
- Monolithic applications without plugin extensibility needs
- Systems where all features are core and tightly coupled by design
When to Employ This Paradigm
- When building platforms, Integrated Development Environments (IDEs), data ingestion pipelines, or marketplaces where third parties need to extend core functionality.
- When the core system requires extreme stability, while extensions and features must evolve and change rapidly.
- When isolating optional dependencies and sandboxing untrusted code provided by plugins is critical.
Adoption Steps
- Define Core Services: Clearly delineate the minimal responsibilities of the microkernel, such as scheduling, component lifecycle management, core domain primitives, and messaging.
- Specify the Plugin Contract: Design and document the formal contract for all plugins, including registration procedures, capability descriptors, lifecycle hooks (e.g., start, stop), and the permission model.
- Build the Extension Loader and Sandbox: Implement the mechanisms for loading extensions, performing version compatibility checks, negotiating capabilities, and isolating plugins to prevent failures from cascading.
- Provide a Software Development Kit (SDK): To facilitate plugin development, provide an SDK with project templates, testing harnesses, and compatibility-checking tools.
- Govern the Release Process: Maintain a clear compatibility matrix between core and plugin versions. Implement an automated regression test suite that validates core functionality against a variety of plugins.
Key Deliverables
- An Architecture Decision Record (ADR) describing the division of responsibilities between the core and plugins, along with the governance model for plugin development and certification.
- Formal documentation for the security and permission model, detailing what capabilities are available to plugins.
- An automated plugin validation pipeline that performs linting, runs tests, and executes the plugin within a sandbox environment.
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.
- today Changed · -1 lines 5b449e4010e7
- 1mo ago Changed · -4 lines 15554e32e1e2
- 2mo ago First seen · 83 lines · 32 tokens per session scan A 9532f5cc2d70
architecture-paradigm-microkernel is a skill published in the GitHub repository athola/claude-night-market (348 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 867 once invoked, about $0.0001 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-09-03.
architecture-paradigm-microkernel compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| architecture-paradigm-microkernelathola/claude-night-market | Skill | 348 | yesterday | MIT | A | 32 | Claude Code |
| plugin-systemellmos-ai/skills | Skill | 9 | 4d ago | MIT | A | 27 | Claude Code, Codex |
| api-designMartinOlivero/saas-builder | Skill | 5 | 26d ago | MIT | A | 118 | Claude Code |
| integrationsMartinOlivero/saas-builder | Skill | 5 | 26d ago | MIT | A | 220 | Claude Code |
| secure-codingMartinOlivero/saas-builder | Skill | 5 | 26d ago | MIT | A | 128 | Claude Code |
| multi-tenancyMartinOlivero/saas-builder | Skill | 5 | 26d ago | MIT | A | 221 | Claude Code |
| authMartinOlivero/saas-builder | Skill | 5 | 26d ago | MIT | A | 121 | Claude Code |