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/verify/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/verify)<a href="https://agentmods.dev/skills/testdino-hq/testdino-mcp/verify"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/verify/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/verify"><img src="https://agentmods.dev/badge/skills/testdino-hq/testdino-mcp/verify.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.00018 | $0.00438 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
verify 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 9d 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.
What it actually says
Run verification for the TestDino MCP project.
Scopes
Quick Gate (after each code change)
Use when: you just modified code and want a fast check.
npm run typecheck && npm run lint
Full Gate (before commit/PR)
Use when: work is complete, ready to commit.
npm run format && npm run typecheck && npm run lint && npm run test && npm run build
Publish Gate (before npm publish)
Use when: preparing a release.
npm run format && npm run typecheck && npm run lint && npm run test && npm run build
Then verify:
- Version is consistent across
package.json,server.json, andsrc/index.ts dist/is up to date (checkgit diff dist/)- No
.envor secrets in staged files
Detection
If $ARGUMENTS is "quick" or "fast" → run Quick Gate.
If $ARGUMENTS is "publish" or "release" → run Publish Gate.
Otherwise → run Full Gate.
Report Format
Scope: quick / full / publish
format: PASS/FAIL/SKIPPED
typecheck: PASS/FAIL
lint: PASS/FAIL
test: PASS/FAIL (N tests, N passed, N failed)
build: PASS/FAIL/SKIPPED
version: CONSISTENT/MISMATCH (publish only)
Rules
- If any check fails: report specific errors with file:line references
- Fix issues before continuing — don't skip failing checks
- format is skipped in quick gate (it modifies files, which may not be desired mid-work)
- build is skipped in quick gate (typecheck catches most issues faster)
- Never suppress warnings to make checks pass
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.
- 9d ago First seen · 66 lines · 18 tokens per session scan A 3067c225ef17
verify is a skill published in the GitHub repository testdino-hq/testdino-mcp (9 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 438 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
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.