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 agentmods add skills/lukasrepublic/agentic-foundry/custody-dataplanenpx skills add lukasrepublic/agentic-foundry --skill custody-dataplanegit 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/custody-dataplane)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/custody-dataplane"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/custody-dataplane.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 | $0.00000 | $0.01020 |
| Opus 5 | $0.00000 | $0.00510 |
| Sonnet 5 | $0.00000 | $0.00204 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade A, and why
custody-dataplane 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 4d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to trigger
- Isolating a custodial/sensitive workload with per-pod security groups (security-groups-for-pods / branch ENI) so the data tier admits ONLY the dedicated pod SG.
- A SecurityGroupPolicy pod stuck
Pendingforever, or a branch-ENI pod whose every outbound connection times out. - Reviewing the first per-pod-SG workload on a cluster (the enablers are cluster-wide substrate — the workload author is the least likely to notice they're absent).
The five silent enablers (ALL must hold; every one fails silently)
- 1 — The VPC-resource-controller policy on the CLUSTER role. The base cluster policy does NOT
grant trunk/branch-ENI creation. Missing ⇒
TrunkENICreationFailed: UnauthorizedOperation, no node advertisespod-enicapacity, and SGP pods stay Pending forever. - 2 — Trunk-CAPABLE worker nodes. A node advertises branch-ENI capacity only if it registered AFTER the IAM policy was live AND ran the CNI with pod-ENI enabled. Pre-existing/bootstrap nodes do NOT retro-attach a trunk — cycle the node or restart its CNI agent so it re-registers. Karpenter-provisioned fresh nodes pick it up automatically once enabler 1 is live.
- 3 — SNAT exclusion for the data/peer CIDRs. Default CNI SNAT sends pod→outside-VPC traffic
out the node primary ENI, which carries the NODE SG, not the pod SG — a data-tier SG
admitting only the pod SG silently drops it (
connection timeout). Exclude the peered/data VPC CIDRs from SNAT so the pod SG survives the hop. - 4 — Node-SG :53 ingress FROM the pod SGs. Cluster DNS sits behind the node SG, whose :53 ingress typically admits only the node SG itself — the branch-ENI pod's DNS queries (sourced from the pod SG) are dropped and resolution hangs. The most-missed enabler: DNS "already works" for every non-branch-ENI pod, and the symptom surfaces as a data-tier timeout.
- 5 — Verify the pod SG's LIVE egress rules were APPLIED — not just authored. An SG that exists and a CR that references it look correct even when the egress rules never landed (a partial apply, a provider that dropped the rule). Assert the LIVE egress rules match intent — distinct from confirming the SG and CR exist.
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.
- 4d ago First seen · 65 lines · 0 tokens per session scan A 75adf569631f
custody-dataplane 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 1,020 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
ccm-expert
CSA CCM expert for cloud security. Deep knowledge of Cloud Security Alliance Cloud Controls Matrix including 197 controls, 17 domains, CAIQ questionnaire, cloud service models (IaaS/PaaS/SaaS), shared responsibility, and framework mappings to ISO 27001, SOC 2, PCI-DSS, NIST.
aws-inspector-expert
Expertise in evaluating AWS accounts for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret aws CLI output.
observability
Metrics, logging, distributed tracing, dashboards, alerting, SLO-driven observability, post-incident analysis. Use when designing monitoring, setting up dashboards, creating alert rules, or analyzing production data.
gcp-inspector-expert
Expertise in evaluating GCP projects for compliance — what checks are meaningful, which SCF controls they map to, and how to interpret gcloud output.
azure-inspector-expert
Expertise in evaluating Azure subscription findings from azure-inspector and mapping them to SCF controls.
enterprise-architecture
Enterprise architecture patterns, multi-tenancy isolation, disaster recovery (RTO/RPO), data residency, and audit logging standards.