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 ccoalm/ccl-skills --skill platform-service-connectivitygit clone --depth 1 https://github.com/ccoalm/ccl-skillsWrote 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/ccoalm/ccl-skills/platform-service-connectivity)<a href="https://agentmods.dev/skills/ccoalm/ccl-skills/platform-service-connectivity"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/platform-service-connectivity/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/ccoalm/ccl-skills/platform-service-connectivity"><img src="https://agentmods.dev/badge/skills/ccoalm/ccl-skills/platform-service-connectivity.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.00052 | $0.05545 |
| Opus 5 | $0.00026 | $0.02772 |
| Sonnet 5 | $0.00010 | $0.01109 |
| Haiku 4.5 | $0.00005 | $0.00554 |
Grade A, and why
platform-service-connectivity 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 3d 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Service Connectivity
- Code/test changes require self-checks; invoke
code-reviewautomatically before completion.
This skill owns how requests move between services: the transport layer (mesh), service discovery, multi-environment routing, retry/timeout/circuit-breaker policy, and the framework middleware that propagates app-level context across hops.
You do not own:
- Whether the right signals exist or how to alert on them — go to
platform-observability. - Whether a change is safe to promote across environments —
platform-release-engineeringconsumes connectivity policy as input. - HTTP handler shape, DB schema, or business contract design — language-specific service-architecture skills.
- Agent/MCP tool exposure, dynamic tool catalog/cache behavior, model-visible schemas, or execution-time tool authorization — route those to
llm-inference-integration. This skill owns the connector's network path, egress policy, mTLS/TLS boundary, service identity, and transport observability, not whether the agent may call a tool.
Skill Routing
- Use this skill for: introducing or auditing service mesh, choosing service-discovery mechanism, setting retry/timeout/circuit-breaker defaults, designing lane-based or canary-based traffic shifts, debugging a "service A can't reach service B" failure, writing connectivity middleware, deciding where mTLS lives, propagating tenant/lane/log-id across hops.
- Use
platform-observabilityfor: anything about whether you can see a connectivity failure (envoy access log, kitex/grpc trace, Prom mesh metrics). - Use
platform-release-engineeringfor: shifting traffic during a deploy, promoting a canary, or rolling back via mesh VirtualService. - Use
llm-inference-integrationfor: agent tool catalogs, MCP tool/resource/prompt semantics, prompt-cache or manifest stability, tool-call approval policy, execution-time authorization, and model-visible connector schemas. Return here only for the connector's network reachability, service identity, egress allowlist, TLS/mTLS, timeout/retry transport policy, or mesh/discovery path. - Use
defect-diagnosisfor: an active connectivity incident — come back here to land the recurring pattern.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 280 B
- references/dual-sidecar-and-traffic-config-center.md 6.2 KB
- references/framework-middleware.md 5.5 KB
- references/grpc-authority-workaround.md 4.6 KB
- references/http-response-envelope-contract.md 1.7 KB
- references/mesh-architecture.md 9.6 KB
- references/multi-env-routing.md 6.2 KB
- references/protobuf-http-contract-signals.md 7.4 KB
- references/retry-timeout-circuit-breaker.md 13 KB
- references/rpc-framework-recipe.md 66 KB
- references/service-discovery-choice.md 9.6 KB
- references/service-discovery-migration-playbook.md 11 KB
- references/service-discovery-recipe.md 7.3 KB
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.
- 3d ago Changed · +2 lines 2d161e919326
- 4d ago Changed 558b1d686452
- 11d ago First seen · 277 lines · 52 tokens per session scan A 17c0927bfaaf
platform-service-connectivity is a skill published in the GitHub repository ccoalm/ccl-skills (6 stars, last pushed today), licensed Apache-2.0. It adds 52 tokens to every session and 5,545 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs. Use when designing or reviewing REST endpoints, resource names, status codes, pagination, or versioning.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
django-security
Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.