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 ngerakines/atproto-skills --skill atproto-publish-lexicongit clone --depth 1 https://github.com/ngerakines/atproto-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/ngerakines/atproto-skills/atproto-publish-lexicon)<a href="https://agentmods.dev/skills/ngerakines/atproto-skills/atproto-publish-lexicon"><img src="https://agentmods.dev/badge/skills/ngerakines/atproto-skills/atproto-publish-lexicon/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/ngerakines/atproto-skills/atproto-publish-lexicon"><img src="https://agentmods.dev/badge/skills/ngerakines/atproto-skills/atproto-publish-lexicon.svg" alt="Reviewed on agentmods" width="80" 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.00387 | $0.03372 |
| Opus 5 | $0.00193 | $0.01686 |
| Sonnet 5 | $0.00077 | $0.00674 |
| Haiku 4.5 | $0.00039 | $0.00337 |
Grade A, and why
atproto-publish-lexicon 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 12d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AT Protocol Lexicon Publication
A lexicon isn't published until it's a record. This skill covers the protocol-level workflow that takes a validated lexicon JSON document, wraps it as a com.atproto.lexicon.schema record, writes it to the authoring DID's repo, and makes it resolvable by NSID. The inverse — consumers resolving an NSID back to a lexicon — is the other half.
Authoring the JSON document itself is the sibling skill atproto-lexicon's job. This skill starts the moment you're ready to put that document on the network.
When to use
- The user is publishing a new lexicon or a revision to an existing one (
putRecord/createRecordoncom.atproto.lexicon.schema). - The user is debugging why their published lexicon doesn't resolve — authority mismatch, missing
_lexicon.TXT, wrong rkey. - The user is consuming a lexicon by NSID at runtime and wants to understand the resolution chain (NSID → authority → DNS → DID → PDS → record).
- The user is planning a breaking change and needs to know how
revisionand the authority model interact.
What this skill provides
- A publish pipeline: form the record, validate, check authority, diff against any prior revision, compute the CID, publish, verify.
- The
com.atproto.lexicon.schemarecord shape — what's top-level, whatidmust equal, whatlexicon: 1means. - The resolution flow for consumers: reverse-DNS the NSID, look up
_lexicon.<authority>TXT, resolve the DID, fetch the record. - The authority model: who's allowed to publish under which NSID prefix, and why the PDS doesn't enforce it.
- Revision discipline: monotonic integers, no semver, how to gate breaking changes.
Detail lives in references/; this file is the procedure.
Procedure
Follow these steps in order. Skipping authority or compatibility checks is how lexicons ship broken.
- Form the record. A
com.atproto.lexicon.schemarecord is the lexicon document with a$typestamped on top. Top-level fields:$type:com.atproto.lexicon.schema(required)lexicon:1— the lexicon language version, fixed at 1 today (not a semver of your doc)id: the NSID, e.g.com.example.foo.getBar— MUST equal the rkey you'll publish underrevision: optional integer; omit for the first publish, bump monotonically thereafterdescription: optional top-level stringdefs: the map of definition names to def objects (main, plus any secondary defs)
What ships with it
5 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.
- 12d ago First seen · 191 lines · 387 tokens per session scan A fa67ab6e0411
atproto-publish-lexicon is a skill published in the GitHub repository ngerakines/atproto-skills (50 stars, last pushed 4mo ago), licensed MIT. It adds 387 tokens to every session and 3,372 once invoked, about $0.0019 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-30.
Other skills, from other repositories
afrexai-api-architect
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
litellm
Operate, configure, secure, and troubleshoot the LiteLLM AI gateway (proxy) and Python SDK: run the proxy (litellm --config), route to 100+ providers through one OpenAI-compatible API, configure model lists and routing/reliability, virtual keys, teams, budgets, rate limits, caching, guardrails, observability, and…
Send and diagnose transactional email through Twilio SendGrid from a terminal or agent: send messages, check deliverability (bounces and spam reports), and verify Signed Event Webhook signatures (ECDSA P-256) — with a bundled email-cli script that is read-only by default and gates every send behind a --dry-run/--yes…
supabase
Use this skill when developing applications with Supabase, running the Supabase CLI, designing migrations and RLS policies, testing database behavior, generating client types, deploying the official self-hosted Docker stack, or administering its Postgres, Auth, Storage, Realtime, Functions, API gateway, backups…
vercel-eve
Build, develop, deploy, self-host, secure, and troubleshoot durable backend AI agents with Vercel Eve. Use when creating an Eve agent, adding tools, skills, subagents, channels, schedules, sandboxing, durable sessions, observability, or deploying Eve on Vercel or a Node host. Do not use for the separate Vercel AI SDK…
agentmail
API-first email platform designed for AI agents. Create and manage dedicated email inboxes, send and receive emails programmatically, and handle email-based workflows with webhooks and real-time events. Use when you need to set up agent email identity, send emails from agents, handle incoming email workflows, or…