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 lukasrepublic/agentic-foundry --skill origin-mtls-wiringgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/origin-mtls-wiring)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/origin-mtls-wiring"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/origin-mtls-wiring.svg" alt="Measured on agentmods" 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.00000 | $0.00768 |
| Opus 5 | $0.00000 | $0.00384 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
origin-mtls-wiring 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to trigger
- Exposing a service to the public internet behind a CDN/edge proxying to a cloud load-balancer origin — especially a sensitive/custody service (origin-mTLS is a hard prerequisite there).
- Debugging an edge TLS-handshake error on an origin pull, or reviewing an origin locked only by CDN IP ranges.
The chain (vendor-neutral; ALB trust stores + CDN authenticated origin pulls are the concrete forms)
- Private Root CA → a trust store attached to the load balancer's 443 listener in VERIFY mode → one per-host (wildcard-CN) leaf CLIENT certificate (clientAuth EKU) uploaded to the CDN's per-hostname origin-pull feature. The origin then accepts ONLY connections bearing the edge provider's cert — "our-zone-only", closing the shared-CDN-IP bypass (the published egress ranges are shared by every tenant of the provider).
- Only
verifyenforces — the permissive/passthrough mode is FAIL-OPEN. The workload chart's toggle whitelists verify/off ONLY, so a typo fails closed instead of silently admitting.
The load-bearing rollout ordering (and its rollback)
- (a) attach the trust store in a no-enforce mode → (b) upload the leaf to the CDN per host →
(c) flip the listener to
verify. Flipping verify BEFORE the CDN presents the cert breaks every handshake for every host on the listener — the ordering is load-bearing, not cosmetic. - Rollback is flipping the listener back to off — one attribute, instant, no cert churn.
The DNS trap (masquerades as an mTLS failure)
- Use an explicit per-host proxied CNAME → the correct origin; a wildcard proxied record is a trap. The wildcard resolves every host to the edge, but its ORIGIN is not the intended load balancer — the origin pull lands off-target and fails with a generic edge TLS-handshake error even though per-host origin-pull is "active".
- Diagnostic rule: listener shows verify + trust store active + zero revoked ⇒ a handshake error is DNS/origin-routing, not the mTLS config.
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.
- 8d ago First seen · 56 lines · 0 tokens per session scan A 793e2f137239
origin-mtls-wiring is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 768 tokens. 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-31.
Other skills, from other repositories
helm-scaffolding
Scaffolds Helm charts for SDD components, driven by component settings.
helm-standards
Standards for Helm charts in SDD projects, including settings-driven patterns.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
spawn-reviewers
Spawn and collect the reviewer fleet at stage20spawnreviewers. Consumes spawn.json.spec (the authoritative spawn spec from derive-spawn-spec / derive-static-spec), resolves GRAPHPROJECT, builds per-agent prompts from the per-agent template + role suffixes (Bug Hunter A/B, Unified Auditor, Domain Critics, Impact…
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…