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/stoa-platform/stoa/cartonpx skills add stoa-platform/stoa --skill cartogit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/carto)<a href="https://agentmods.dev/skills/stoa-platform/stoa/carto"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/carto.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.01172 |
| Opus 5 | $0.00000 | $0.00586 |
| Sonnet 5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade C, and why
carto scanned grade C with 1 finding 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 5d 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.
Harvests environment variableshighData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
Extract secrets mapping from the catalog: How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/carto — Platform Service Catalog
Query the STOA platform service catalog for live infrastructure state.
Modes
| Command | What it does |
|---|---|
/carto or /carto all |
Full inventory — all services with deploy status |
/carto <service> |
Detail view of a single service + live state |
/carto drift |
Run drift detection (catalog vs K8s live) |
/carto graph |
Show the Mermaid dependency graph |
/carto secrets |
Show secrets-to-services mapping |
Step 1: Read the Catalog
The catalog lives in stoa-infra (private repo), NOT in the public stoa repo.
Locate and read the catalog in this order:
~/hlfh-repos/stoa-infra/docs/platform-catalog.yaml(local clone — preferred)- If not found:
docs/platform-catalog.yaml(legacy location in stoa repo — may be stale) - If neither exists: warn the user and suggest cloning stoa-infra
Important: When updating the catalog (drift fixes, new services), always write to stoa-infra/docs/platform-catalog.yaml. NEVER commit infra topology (hosts, IPs, clusters, secrets) to the public stoa repo.
Step 2: Execute Based on Mode
Mode: all (default)
- Read the full catalog
- For each service, format a summary line:
## Platform Inventory — {metadata.lastUpdated}
### Core Services (K8s)
| Service | Type | Port | Prod Replicas | Health | ArgoCD |
|---------|------|------|---------------|--------|--------|
| control-plane-api | backend | 8000 | 2 | /health | control-plane-api |
| ... | ... | ... | ... | ... | ... |
### External Services (VPS)
| Service | Type | Host | Purpose |
|---------|------|------|---------|
### Clusters
| Cluster | Provider | Nodes |
|---------|----------|-------|
- If kubectl is available, enrich with live status:
kubectl get deployments -n stoa-system -o custom-columns='NAME:.metadata.name,READY:.status.readyReplicas,IMAGE:.spec.template.spec.containers[0].image' 2>/dev/null
Mode: <service> (single service detail)
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.
- 5d ago First seen · 147 lines · 0 tokens per session scan C 87ec35b7d6e2
carto is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,172 tokens. A static security scan graded it C with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
docker
Docker container management.
helm-update
Apply helm chart updates for Bifrost. Detects config.schema.json changes since the last helm release, applies user-requested changes, updates values.yaml / values.schema.json / helpers.tpl, bumps Chart.yaml version, updates helm README (Latest Version + Upcoming section), creates a docs MDX changelog, and updates…
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.