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 bolivian-peru/os-moda --skill service-explorergit clone --depth 1 https://github.com/bolivian-peru/os-modaWrote 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/bolivian-peru/os-moda/service-explorer)<a href="https://agentmods.dev/skills/bolivian-peru/os-moda/service-explorer"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/service-explorer/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/bolivian-peru/os-moda/service-explorer"><img src="https://agentmods.dev/badge/skills/bolivian-peru/os-moda/service-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 17 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00039 | $0.00506 |
| Opus 5 | $0.00019 | $0.00253 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
service-explorer scanned grade A 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:<port>/ | jq . What it actually says
Service Explorer Skill
You can discover and interact with any service on this system. You are not limited to pre-built integrations.
Discovery
List all running services
system_query({ query: "services" })
Find what's listening on which ports
Check ss -tlnp for all listening TCP sockets with the process that owns them.
Read a service's configuration
For NixOS services: check the relevant NixOS module options.
For config files: read /etc/<service>/config or similar.
Read a service's logs
journalctl -u <service-name> -n 100 --output=json
Interaction
HTTP/REST APIs
If a service exposes an HTTP API on localhost:
curl -s http://localhost:<port>/ | jq .
curl -s http://localhost:<port>/api/v1/health | jq .
Explore endpoints. Read API docs if available.
Databases
# PostgreSQL
psql -U postgres -c "SELECT datname FROM pg_database;"
# Redis
redis-cli PING
redis-cli INFO
Docker/Podman
podman ps -a --format json
podman logs <container>
podman stats --no-stream --format json
Principle
You don't need a pre-built plugin for every service. You have full system access. Read configs. Hit APIs. Parse logs. Figure it out. Discover. Explore. Report back to the user.
Remember
When you discover a new service or learn how to interact with it, store that knowledge:
memory_store({
summary: "Discovered Prometheus on port 9090",
detail: "Prometheus running at localhost:9090. API at /api/v1/. Key endpoints: /query, /targets, /alerts. Configured to scrape node_exporter and agentd.",
category: "system.service",
tags: ["prometheus", "monitoring", "discovery"]
})
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.
- 11d ago First seen · 80 lines · 39 tokens per session scan A dd2540576994
service-explorer is a skill published in the GitHub repository bolivian-peru/os-moda (117 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 39 tokens to every session and 506 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-cloud-storage-access-patterns
Detect abnormal access patterns in AWS S3, GCS, and Azure Blob Storage by analyzing CloudTrail Data Events, GCS audit logs, and Azure Storage Analytics. Identifies after-hours bulk downloads, access from new IP addresses, unusual API calls (GetObject spikes), and potential data exfiltration using statistical baselines…
aws-patterns
Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.
azure-patterns
Azure Functions, Cosmos DB modeling, Service Bus patterns, Bicep templates.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
hono-api-scaffolder
Scaffold Hono API routes for Cloudflare Workers. Produces route files, middleware, typed bindings, Zod validation, error handling, and APIENDPOINTS.md documentation. Use after a project is set up with cloudflare-worker-builder or vite-flare-starter, when you need to add API routes, create endpoints, or generate API…
cloudflare-worker-builder
Scaffold and deploy Cloudflare Workers with Hono routing, Vite plugin, and Static Assets. Describe project, scaffold structure, configure bindings, deploy. Use whenever the user wants to create a Worker project, set up Hono on Cloudflare, configure D1 / R2 / KV / Queues bindings, or troubleshoot Worker export syntax…