Borrowing it
Nothing to install: this file belongs to dogganidhal/noddde. 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/dogganidhal/noddde/main/.claude/skills/run-tests/SKILL.mdgit clone --depth 1 https://github.com/dogganidhal/nodddeWrote 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/dogganidhal/noddde/run-tests)<a href="https://agentmods.dev/skills/dogganidhal/noddde/run-tests"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/run-tests/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/dogganidhal/noddde/run-tests"><img src="https://agentmods.dev/badge/skills/dogganidhal/noddde/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- medium MCP Rug Pull · line 31 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 47 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00037 | $0.00749 |
| Opus 5.5 | $0.00015 | $0.00300 |
| Sonnet 5.5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
run-tests 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 2mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 4: Run Tests (GREEN Phase)
Run the test suite and report whether the RED tests from step 2 are now GREEN.
Pipeline step 4 of 6. Called by the /spec orchestrator after step 3 (implementation). Loops back to step 3 if tests are RED.
Step 1: Determine What to Run
If a spec path is provided: Find the corresponding test file:
specs/core/<path>/<name>.spec.md→packages/core/src/__tests__/<path>/<name>.test.tsspecs/integration/<name>.spec.md→packages/core/src/__tests__/integration/<name>.test.ts
If a module name is provided: Find test files matching:
packages/core/src/__tests__/**/<module-name>*.test.ts
If nothing is provided: Run the full test suite.
Step 2: Run Type Check
cd packages/core && npx tsc --noEmit
Report any type errors. Type errors must be fixed before tests can meaningfully pass.
Step 3: Run Tests
For a specific test file:
cd packages/core && npx vitest run --reporter=verbose <test-file-path>
For the full suite:
cd packages/core && npx vitest run --reporter=verbose
Step 4: Analyze Results
Categorize the outcome:
All GREEN
Every test passes. The implementation matches the spec.
✅ All tests GREEN: <test-file-path>
Type check: ✅ passing
Tests: <N>/<N> passing
Next step:
Run `/validate-spec <spec-path>` for the final cross-check.
Some RED
Some tests still fail. The implementation is incomplete or incorrect.
🔴 Some tests still RED: <test-file-path>
Type check: ✅ passing / ❌ N errors
Tests: <passing>/<total> passing, <failing> failing
Failing tests:
1. "<test name>" — <error message summary>
2. "<test name>" — <error message summary>
Analysis:
- <for each failure, identify whether it's a missing implementation,
a bug in the implementation, or a test code issue>
Next step:
Fix the implementation and run `/run-tests <spec-path>` again.
If a test itself is wrong, update the spec first via `/edit-spec`.
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.
- 2mo ago First seen · 119 lines · 37 tokens per session scan A 43cd98b91dc5
run-tests is a skill published in the GitHub repository dogganidhal/noddde (52 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 749 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
vitest
Use when writing or debugging Vitest assertions, vi mocks, fake timers, snapshots or runner configuration. Not for test-first methodology, HTTP interception or Jest-only APIs; use tdd or msw where applicable.
cratis-application-slice-specifications
Use when choosing backend plain-call or pipeline-scenario coverage for an event-sourced Cratis application slice. Not for frontend interactions or language-level framework specification mechanics.
cratis-chronicle-event-constraints
Use when Chronicle uniqueness or create-once rules must hold across concurrent appends from every writer. Not for ordinary input validation, capacity predicates or projection creation.
cratis-chronicle-read-model-specifications
Use when specifying how Chronicle events become read-model state, including projection or reducer wiring and pure reducer decisions. Not for creating the production model or testing raw event append behavior.
cratis-application-react-specifications
Use when specifying a Cratis application's React view-model decisions, command orchestration or narrow component interactions. Not for backend pipeline scenarios or framework-package specifications.
cratis-chronicle-event-specifications
Use when specifying Chronicle event appends or constraint violations through the in-process append path. Not for command handling or how events become read-model state.