customising-jason SKILL.md skillA
customising-jason from reply-team/jason-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add reply-team/jason-ai/customising-jason@git:20261114.6b52d5cPins git:20261114.6b52d5c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- reply-team/jason-ai
- Path
skills/runtime/customising-jason/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261114.6b52d5c, committed Nov 14, 2026
- Size
- 13,784 bytes
- Repository stars
- 9
- License
- MIT
Use when a person asks to change how Jason itself works rather than to do campaign work - make a role write or behave differently, add a role, add or change a plugin for a service they use, send an operation to another plugin, or grant a plugin what it needs - and to say what an update keeps and what is never touched.
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
# Customising Jason If you cannot write to the role skills folder from where you run, say so, and tell the person to choose Open in › Change Jason itself in Jason's window, or to run `jason session open --setup` in a terminal. The desktop's chat is one such place: it is kept from changing Jason's own files, and on Codex it can read them but not change them. This skill is about changing Jason itself: the instructions its roles work by, the plugins that perform provider work, where an operation's work goes, and what a plugin may reach. It is not about campaign work, which is `managed-campaign-work`, and not about running the installation, which is `operating-the-installation`. A person reaches it by saying what they want different, for example "make the copywriter write shorter in every campaign" or "add a plugin for my CRM". Ask what they want changed if they have not said, change exactly that, and say afterwards where the change now takes effect. **Status: draft.** Its commands parse against this build. ## Read where the parts are Never assume a folder. Ask the installation: ``` jason status --human ``` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_mad4pwknhxytcwxb/8ac248650f734c44dc3267faef7ca1b90d2a2e4b2771bcba60e0e7c083298336.json
Then /plugin install customising-jason@markdownregistry-mad4pwknhxytcwxb in Claude Code. It installs git:20261114.6b52d5c, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add reply-team/jason-ai/customising-jason@sha256:8ac248650f734c44The line at the top of this page pins the label git:20261114.6b52d5c, 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_mad4pwknhxytcwxb)
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 reply-team/jason-ai/customising-jason 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 customising-jason from somewhere else? Ask it: where did my customising-jason 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 1 version of this file, committed on Nov 14, 2026.
Watch this file (sign in, one email per new version)
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/customising-jason/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 (13784 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
reply-team/jason-ai · 9 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mad4pwknhxytcwxb GET https://markdownregistry.com/api/v1/resolve?ref=reply-team/jason-ai/customising-jason GET https://markdownregistry.com/api/v1/blob/8ac248650f734c44dc3267faef7ca1b90d2a2e4b2771bcba60e0e7c083298336
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.