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/registering-servicesnpx skills add desirecore/market --skill registering-servicesgit clone --depth 1 https://github.com/desirecore/marketWrote 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/desirecore/market/registering-services)<a href="https://agentmods.dev/skills/desirecore/market/registering-services"><img src="https://agentmods.dev/badge/skills/desirecore/market/registering-services.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.00076 | $0.02054 |
| Opus 5 | $0.00038 | $0.01027 |
| Sonnet 5 | $0.00015 | $0.00411 |
| Haiku 4.5 | $0.00008 | $0.00205 |
Grade A, and why
registering-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 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.
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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
registering-services Skill
L0: One-line Summary
Tell the Agent how to register an external HTTP/MCP service into the global catalog with human governance.
L1: Overview
This meta-skill teaches you (the Agent) how to add a new service to the
shared "Apps & Services" catalog. It does not invoke external services
itself — once registered, use the per-service Skill at ~/.desirecore/skills/svc-<id>/
or the using-services meta-skill to actually call them.
When to use this skill
- The user asks to register an API or service (e.g. "add the Acme search endpoint to our catalog")
- You just deployed a backend you want other Agents to be able to reach
- You discover a useful public API and want to make it shareable
When NOT to use it
- One-off HTTP calls that nobody else needs to repeat — just call
HttpRequestdirectly - Adding an MCP server to your own agent only — POST to
/api/agents/<your-id>/mcp-serversinstead, no catalog entry needed - Modifying an existing catalog entry — the user must promote/reject through the Store UI
L2: How to register a service
Step 1 — Gather the required fields
Before calling the API, collect:
| Field | Required | Notes |
|---|---|---|
id |
yes | kebab-case, globally unique (e.g. acme-search-api) |
name |
yes | Human-readable display name |
description |
yes | One sentence — what it does |
protocol |
yes | 'http' or 'mcp' |
tags |
yes | Searchable list, e.g. ['search', 'web'] |
registeredBy |
yes | Your own agent id |
endpoint |
required when protocol='http' |
Base URL of the API |
riskLevel |
recommended | low / medium / high / critical |
auth |
when API requires auth | { type, secretRef } — see below |
operations |
recommended | Operations list for the per-service Skill |
capabilities |
optional | What this service can do |
Step 2 — Choose riskLevel honestly
riskLevel decides whether future calls to this service trigger an
approval gate:
What ships with it
2 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.
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 · 202 lines · 76 tokens per session scan A d9ce5a407f87
registering-services is a skill published in the GitHub repository desirecore/market (2 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,054 once invoked, about $0.0004 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
skill-router
Find the right skill in the PCL standard library and compose several when a task spans domains. Use when the user asks which skill applies, cannot find a capability, wants to know what the library covers, is starting a task that spans several domains, or when the task involves choosing between overlapping skills…
social-commerce
Sync your catalog to Instagram, TikTok, and Facebook to enable shoppable posts and in-app checkout directly from your social content.
antigravity-skill-orchestrator
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
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.
llamaguard
Meta's 7-8B specialized moderation model for LLM input/output filtering. 6 safety categories - violence/hate, sexual content, weapons, substances, self-harm, criminal planning. 94-95% accuracy. Deploy with vLLM, HuggingFace, Sagemaker. Integrates with NeMo Guardrails.
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…