apx-extensions SKILL.md skillA
apx-extensions from agentprojectcontext/apx is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add agentprojectcontext/apx/apx-extensions@git:20261008.ed82b79Pins git:20261008.ed82b79 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- agentprojectcontext/apx
- Path
apps/terminal/skills/apx-extensions/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261008.ed82b79, committed Oct 8, 2026
- First version recorded
- Oct 5, 2026
- Size
- 5,588 bytes
- Repository stars
- 35
- License
- MIT
Builds an APX extension — one folder with an `apx-extension.json` that brings skills, MCP servers, routine templates, secrets the owner types once and, optionally, a sandboxed plugin — then checks and installs it with `apx extensions inspect|install|on`. Also says when an extension is the wrong tool (a project skill, an agent template, a plain MCP server). Triggers: 'APX extension', 'make an extension for APX', 'apx-extension.json', 'APX plugin', 'package skills for APX', 'add an MCP to APX as…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Building an APX extension
An extension is a folder APX can read **without running anything**: a manifest (`apx-extension.json`) plus the files
it names. It installs **off**; turning it on approves exactly those files.
## Pick the smallest thing first
| The owner wants | Make |
|---|---|
| Know-how for this one project's agents | A skill in the project: `.apc/skills/<name>/SKILL.md` — no extension |
| One more MCP server for their own agents | `apx mcps add <name> <command…|url>` — no extension |
| An agent (or a team) with its own routines | An agent template: `<slug>.md` + `<slug>.routines.json` |
| Skills, servers and routines that travel together, shared or reused | **An extension** |
| Code that watches events or adds context to the owner's turns | An extension with a `plugin` |
## The folder
```
northwind-crm/
apx-extension.json
skills/
crm-lookup/SKILL.md # each skill: a folder with a SKILL.md (frontmatter name + description)
server.mjs # only if an MCP server runs from the folder ("./server.mjs")
plugin.mjs # only if there is a plugin
```
## `apx-extension.json`
Unknown keys are refused (the schema is strict).
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_lokkmedgfjywvflw/b68c1eba3be5616f7a3432707638b27948923b9bd4f1c46d9d340950cbde216e.json
Then /plugin install apx-extensions@markdownregistry-lokkmedgfjywvflw in Claude Code. It installs git:20261008.ed82b79, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add agentprojectcontext/apx/apx-extensions@sha256:b68c1eba3be5616fThe line at the top of this page pins the label git:20261008.ed82b79, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_lokkmedgfjywvflw)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in agentprojectcontext/apx/apx-extensions since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of apx-extensions from somewhere else? Ask it: where did my apx-extensions come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Oct 5, 2026 and Oct 8, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.ed82b79 latest | 2026-10-08 | ed82b79 | 5,588 B | A | view · diff |
| git:20261005.a39371d | 2026-10-05 | a39371d | 5,509 B | A | view · diff |
| git:20261005.19b37ce | 2026-10-05 | 19b37ce | 5,587 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/apx-extensions/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5588 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
agentprojectcontext/apx · 35 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lokkmedgfjywvflw GET https://markdownregistry.com/api/v1/resolve?ref=agentprojectcontext/apx/apx-extensions GET https://markdownregistry.com/api/v1/blob/b68c1eba3be5616f7a3432707638b27948923b9bd4f1c46d9d340950cbde216e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from agentprojectcontext/apx
Every file in agentprojectcontext/apx