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/desirecore/market/using-servicesnpx skills add desirecore/market --skill using-servicesgit clone --depth 1 https://github.com/desirecore/marketWhat 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.00069 | $0.01762 |
| Opus 5 | $0.00034 | $0.00881 |
| Sonnet 5 | $0.00014 | $0.00352 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
using-services 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 2d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
using-services Skill
L0: One-line Summary
Teach the Agent how to look up and call services from the global "Apps & Services" catalog.
L1: Overview
The "Apps & Services" catalog stores all registered HTTP/MCP services. This
meta-skill is your manual for finding the right service and invoking
it correctly. Each non-trivial registered service also has its own
svc-<id> Skill auto-generated from its operations — prefer that when it
exists; this meta-skill is the fallback for ad-hoc discovery.
When to use
- The user asks you to do something that might already have a registered service (e.g. "search the product database", "send a notification")
- You see
svc-<id>Skill in your available skills list — activate it directly - You need to call an HTTP API and want to check if it's been registered (to benefit from governance, credential injection, and audit)
When NOT to use
- The user gives you a one-off URL to fetch — use
HttpRequestdirectly - You already have the per-service
svc-<id>Skill activated — follow it instead, it's more specific
L2: How to discover and call
Step 1 — List the catalog
Fetch the registry:
tool: HttpRequest
parameters:
url: http://127.0.0.1:<agent-service-port>/api/registry/services
method: GET
Response shape (excerpt):
{
"data": {
"services": [
{
"id": "acme-search-api",
"name": "Acme Search API",
"protocol": "http",
"endpoint": "https://api.acme.example/search",
"tags": ["search", "products"],
"status": "online",
"origin": "agent",
"reviewStatus": "approved",
"riskLevel": "medium",
"operations": [...]
}
],
"total": 1,
"source": "official"
}
}
Step 2 — Pick a candidate
Filter by tags, protocol, name. Important checks before invoking:
status === 'online'→ safe to callstatus === 'offline'/'error'→ tell the user the service is down, don't retry blindlystatus === 'degraded'→ degrade gracefully, mention it to the userreviewStatus === 'pending'(onlyorigin='agent') → you can only call it ifregisteredByis you; otherwise ask the user to promote itriskLevel === 'critical'→ expect a human approval prompt on every call
What ships with it
1 file 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.
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.
- 2d ago First seen · 188 lines · 69 tokens per session scan A a1b62616687f
using-services is a skill published in the GitHub repository desirecore/market (2 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 1,762 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
portaljs-add-resource
Add another file (resource) to an EXISTING dataset in a PortalJS portal — a data dictionary, methodology, or an additional data file. Turns a single-file dataset into a multi-resource one; the showcase renders a section per resource. Use when a dataset needs a second file, such as a data dictionary, methodology doc…
portaljs-connect-ckan
Wire a scaffolded PortalJS portal to a CKAN backend over its API. Generates a tiny server-side fetch client (no runtime dependency) and feeds the /search catalog and /@namespace/slug showcases from CKAN instead of datasets.json. Use when connecting an existing portal to a live CKAN instance instead of a static…
skill-authoring
Author SKILL.md skills: frontmatter, validator limits, structure.
pentest-playbook
7-phase pentest pipeline from passive recon to exploitation.
tls-fingerprint-impersonation
Spoof TLS ClientHello and JA4 fingerprints for browser impersonation.
torchforge-rl-training
Provides guidance for PyTorch-native agentic RL using torchforge, Meta's library separating infra from algorithms. Use when you want clean RL abstractions, easy algorithm experimentation, or scalable training with Monarch and TorchTitan.