Borrowing it
Nothing to install: this file belongs to hoangsonww/DevVerse-SWE-Blog. 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/hoangsonww/DevVerse-SWE-Blog/master/.agents/skills/devverse-validate/SKILL.mdgit clone --depth 1 https://github.com/hoangsonww/DevVerse-SWE-BlogWrote 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/hoangsonww/devverse-swe-blog/devverse-validate)<a href="https://agentmods.dev/skills/hoangsonww/devverse-swe-blog/devverse-validate"><img src="https://agentmods.dev/badge/skills/hoangsonww/devverse-swe-blog/devverse-validate.svg" alt="Measured on agentmods" 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.00032 | $0.00274 |
| Opus 5 | $0.00016 | $0.00137 |
| Sonnet 5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
devverse-validate 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 yesterday.
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
DevVerse Validation Workflow
-
Inspect the current diff first. Use
git status --shortandgit diff --name-only. -
Read the validation matrix before running commands. @references/validation-matrix.md
-
Choose the smallest useful set of validations that matches the touched files.
-
Never use
npm run lintas a read-only validation step. It runs Prettier write mode in this repository. -
Prefer the constrained-environment Jest commands when needed. Use
env JEST_USE_WATCHMAN=0 npm test -- --runInBand --watchman=false. -
Run
python3 scripts/check_content_contract.pyfor article changes. -
Run
npx tsc --noEmit --pretty falsefor TypeScript, route, component, or library changes. -
Run
npm run buildfor page, layout, config, or global styling changes when it is worth the extra cost. If it fails because of Google font fetching, report that as an environment limitation unless there is evidence of a code regression. -
Report exactly what ran, what passed, what failed, and what was skipped.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 30 lines · 32 tokens per session scan A 8e15c593f2b0
devverse-validate is a skill published in the GitHub repository hoangsonww/DevVerse-SWE-Blog (15 stars, last pushed 20d ago), licensed MIT. It adds 32 tokens to every session and 274 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
pytest-suite
Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.
authoring-data-quality-checks
Adds and runs data quality checks (dbt-test style assertions) on a project's warehouse tables and saved-query views: not-null, uniqueness, accepted values, referential integrity, row-count bounds, freshness, and custom HogQL. Use when asked to test a model, validate a view, check for nulls or duplicates, add data…
JavaScript Testing Patterns
Modern JavaScript testing strategies with Jest, Mocha, and testing best practices covering unit testing, integration testing, mocking, async patterns, and DOM testing.
Jasmine Testing
BDD-style JavaScript testing with Jasmine covering spies, async patterns, custom matchers, clock manipulation, and comprehensive test organization for frontend and Node.js applications.
add-test
Add tests following project test patterns.
jest-expert
Expert in Jest unit testing framework, mocks, snapshots, coverage reports, watch mode, and custom matchers. Use when the user mentions testing, unit testing, JavaScript, QA, mocking, or snapshots, or when the task involves Jest Framework, Test Structure, Advanced Features, or Basic Unit Tests.