Project: Tag Version SKILL.md skillA
Project: Tag Version from jasonwarrenuk/goblin-mode is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jasonwarrenuk/goblin-mode/Project: Tag Version@git:20261104.4299707Pins git:20261104.4299707 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jasonwarrenuk/goblin-mode
- Path
skills/project-tag_version/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261104.4299707, committed Nov 4, 2026
- First version recorded
- Aug 12, 2026
- Size
- 3,356 bytes
- Repository stars
- 6
- License
- none declared
Tag the release after a merge to main, computing the next semver tag with svu.
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
# Tag the release with `svu` [`svu`](https://github.com/caarlos0/svu) derives the next semver tag from conventional-commit history. It only computes the version; it never commits, pushes or merges. **Hard rule:** the tag always comes from `safe-version-next.sh`, never bare `svu next`. The script is identical to `svu next` except it refuses to cross 0.x → 1.x automatically; declaring the API stable is a human decision, so it emits a 0.x minor bump instead (and says so on stderr; relay the note when it fires). Later major bumps pass through. ## The one tagging moment: merge to `main` A release is a commit on `main`; nothing else gets a tag. No tagging at PR creation (the version would point at unreviewed commits, race other open PRs and burn numbers on branches that may never merge), no tagging mid-branch, no plain-semver tags on `staging` (two branches sharing one version sequence means the same number can point at different commits). From an **up-to-date main checkout** (`git checkout main && git pull` first if there's any doubt; tagging from a feature branch or stale main tags the wrong commit): ```bash …
Read the whole file at its exact version.
How to install
mdr add jasonwarrenuk/goblin-mode/Project: Tag Version@sha256:fecadea9065882e7The line at the top of this page pins the label git:20261104.4299707, 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_6cbm3vcwt6o2upu3)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Aug 12, 2026 and Nov 4, 2026, about one every 9 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261104.4299707 latest | 2026-11-04 | 4299707 | 3,356 B | A | view · diff |
| git:20261008.c2dff9e | 2026-10-08 | c2dff9e | 3,151 B | A | view · diff |
| git:20261008.2a2078c | 2026-10-08 | 2a2078c | 3,086 B | A | view · diff |
| git:20260930.dc02fb4 | 2026-09-30 | dc02fb4 | 3,086 B | A | view · diff |
| git:20260910.acd60e5 | 2026-09-10 | acd60e5 | 3,085 B | A | view · diff |
| git:20260819.c70a3ae | 2026-08-19 | c70a3ae | 3,086 B | A | view · diff |
| git:20260814.769885b | 2026-08-14 | 769885b | 2,835 B | A | view · diff |
| git:20260813.b105a8f | 2026-08-13 | b105a8f | 2,847 B | A | view · diff |
| git:20260813.199d770 | 2026-08-13 | 199d770 | 2,731 B | A | view · diff |
| git:20260812.866d73a | 2026-08-12 | 866d73a | 2,709 B | A | view |
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 (3356 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
jasonwarrenuk/goblin-mode · 6 stars · license none declared · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6cbm3vcwt6o2upu3 GET https://markdownregistry.com/api/v1/resolve?ref=jasonwarrenuk/goblin-mode/Project: Tag Version GET https://markdownregistry.com/api/v1/blob/fecadea9065882e75835b0b98fa21d4e7382b2414f5359402332621b3e4dacbf
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.