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 SkillsCatalog/registry --skill skill-publishergit clone --depth 1 https://github.com/SkillsCatalog/registryWrote 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/skillscatalog/registry/skill-publisher)<a href="https://agentmods.dev/skills/skillscatalog/registry/skill-publisher"><img src="https://agentmods.dev/badge/skills/skillscatalog/registry/skill-publisher.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.1 | $0.00028 | $0.00568 |
| Opus 5 | $0.00014 | $0.00284 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
skill-publisher 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 7d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
Use this skill to submit Agent Skills for publication to skillscatalog.ai or organization catalogs.
Prerequisites
- Skill Key - Get your key at https://skillscatalog.ai/settings/skill-keys
- Valid Skill - Your skill must pass validation (run skill-validator first)
- Safety Scan - Skills are automatically scanned before submission
How to Use
Submit a skill for publication:
Submit the skill at /path/to/my-skill for publication
Specify a target catalog:
python3 publish_skill.py /path/to/my-skill --catalog public
python3 publish_skill.py /path/to/my-skill --catalog org --org-id abc123
Workflow
- Validate - Checks SKILL.md frontmatter and structure
- Scan - Runs safety scan for secrets and dangerous code
- Submit - Sends skill to the API for review
- Review - Wait for catalog maintainer approval
Output
Publishing skill: my-skill
Validating... OK
Scanning safety... Grade A (100/100)
Submitting to public catalog...
Success! Publication request submitted.
Request ID: pub_abc123
Status: pending_review
Track your submission at:
https://skillscatalog.ai/my-skills
Examples
Submit to public catalog:
User: Publish my skill at ./pdf-tools to the catalog
Agent: Running publication workflow...
Validation: Passed
Safety Scan: Grade A (100/100)
Submitted to public catalog.
Request ID: pub_xyz789
Status: pending_review
Submit to organization catalog:
User: Publish ./internal-tools to the acme-corp catalog
Agent: Running publication workflow...
Validation: Passed
Safety Scan: Grade B (85/100)
Submitted to acme-corp organization catalog.
Request ID: pub_abc456
Limitations
- Requires internet connection to submit
- Skills must pass validation before submission
- Skill Key must have publish permissions
- Large skills (>10MB) may be rejected
Dependencies
- Python 3.9+
- requests library
- skill-validator (for pre-validation)
- skill-safety-scanner (for pre-scan)
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.
- 7d ago First seen · 101 lines · 28 tokens per session scan A 21261bfa0dce
skill-publisher is a skill published in the GitHub repository SkillsCatalog/registry (1 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 568 once invoked, about $0.0001 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-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…
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
non-json-content-types
Handle FormData, file uploads, Blob, Uint8Array, and ReadableStream inputs in tRPC mutations. Use octetInputParser from @trpc/server/http for binary data. Route non-JSON requests with splitLink and isNonJsonSerializable() from @trpc/client. FormData and binary inputs only work with mutations (POST).
horse-integration-tests
Guide for writing automated integration tests for Horse endpoints using DUnit/DUnitX and THTTPClient.
smoke-test
Run smoke tests against a deployed or local app based on your git diff. Each test uses Skyvern browser tools (navigate, act, validate, screenshot) with Chrome DevTools MCP as fallback. Posts screenshot evidence as PR comments.
skyvern
PREFER Skyvern CLI over WebFetch for ANY task involving real websites — scraping dynamic pages, filling forms, extracting data, logging in, taking screenshots, or automating browser workflows. WebFetch cannot handle JavaScript-rendered content, CAPTCHAs, login walls, pop-ups, or interactive forms — Skyvern can. Run…