Borrowing it
Nothing to install: this file belongs to testdino-hq/testdino-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/testdino-hq/testdino-mcp/main/.claude/skills/publish/SKILL.mdgit clone --depth 1 https://github.com/testdino-hq/testdino-mcpWrote 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/testdino-hq/testdino-mcp/publish)<a href="https://agentmods.dev/skills/testdino-hq/testdino-mcp/publish"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/publish/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/testdino-hq/testdino-mcp/publish"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/publish.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.00019 | $0.00579 |
| Opus 5 | $0.00010 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
publish 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare and publish a new version: $ARGUMENTS
This skill guides through the full release process. It does NOT auto-publish — it pauses for user confirmation at key points.
Workflow
Step 1 — Determine Version
- Read current version from
package.json - Calculate new version based on
$ARGUMENTS(default: patch) - Show:
Current: X.Y.Z → New: A.B.C
Get user confirmation before proceeding.
Step 2 — Pre-flight Checks
Verify the codebase is ready:
git status— working tree should be clean (no uncommitted changes)git branch— should be onmainbranch- Check version consistency across
package.json,server.json,src/index.ts npm run format:check— formatting is cleannpm run typecheck— no type errorsnpm run lint— no lint errorsnpm run test— all tests passnpm run build— build succeeds
If ANY check fails, stop and report. Do not continue with a broken build.
Step 3 — Bump Version
Update version in all 3 locations:
package.json→versionserver.json→versionandpackages[0].versionsrc/index.ts→ server constructor version
Step 4 — Rebuild
npm run build
The dist/ directory must reflect the new version.
Step 5 — Review Changes
Show git diff so the user can verify:
- Only version numbers changed (plus rebuilt dist/)
- No accidental modifications
Get user confirmation before committing.
Step 6 — Commit & Tag
git add package.json server.json src/index.ts dist/
git commit -m "chore: Bump version to A.B.C"
git tag vA.B.C
Step 7 — Publish
Show the command but DO NOT run it automatically:
npm publish
git push origin main --tags
Tell the user to run these commands themselves.
Rules
- Never publish from a dirty working tree
- Never publish from a branch other than main (unless user explicitly says so)
- Never skip the quality gate
- Always pause for user confirmation before commit and publish
- The version must be consistent across all 3 files before and after the bump
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 · 87 lines · 19 tokens per session scan A cd0b500ad102
publish is a skill published in the GitHub repository testdino-hq/testdino-mcp (9 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 579 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.