Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/dogganidhal/noddde/run-testsnpx skills add dogganidhal/noddde --skill run-testsgit 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.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.00037 | $0.00749 |
| Opus 5 | $0.00018 | $0.00375 |
| Sonnet 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 6d 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.
- 6d ago First seen · 119 lines · 37 tokens per session scan A 43cd98b91dc5
run-tests is a skill published in the GitHub repository dogganidhal/noddde (48 stars, last pushed 6d ago), licensed MIT. It adds 37 tokens to every session and 749 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-08-30.
Other skills, from other repositories
gh-issue-organizer
GitHub Issue の棚卸し・整理を体系的に実行するスキル。オープンイシューの分類、 グルーピング、クローズ判定、優先度付け、バッチ化を行う。 CodeRabbit 自動生成イシューと手動報告イシューの区別、根本原因別グルーピング、 完了済みイシューの特定とクローズ提案を含む。 トリガー：「イシューを整理して」「issue を棚卸し」「GitHub issue をトリアージ」 「stale issue をクローズ」「issue の優先度付け」 といった GitHub Issue 整理関連リクエストで起動。.
git-commit
ワーキングディレクトリの変更をConventional Commitsに従ってコミットするスキル。 意味のある変更単位ごとにステージングし、英語でコミットメッセージを作成する。 co-authorやエージェント名をコミットメッセージに含めない。 ユーザーが「コミットして」「変更をコミット」「git commit」「commitして」 「この変更をコミット」「コミットメッセージを書いて」「コミットお願い」 などコミット関連のリクエストをした場合に必ず使用すること。 pushは含まない（コミットのみ）。.
cratis-specs-csharp
Step-by-step guidance for writing C# specs in Cratis with BDD Specification by Example — the Establish/Because/should pattern, for/when/and folder hierarchy, reusable given/ contexts, NSubstitute mocking, and the in-process scenario family. Use when writing C# unit or integration specs or structuring the for/when/and…
write-specs-events
Use this skill when asked to write tests or specs for event appending, event log behavior, constraint violations, or concurrency violations using EventScenario in a Cratis-based project. Produces infrastructure-free in-process specs using EventScenario and AppendResult Should extensions.
cratis-specs-typescript
Step-by-step guidance for writing TypeScript specs in Cratis using BDD-style Specification by Example — the given()/describe/it pattern, for/when/ folder hierarchy, reusable context classes, Sinon mocking, and Chai assertions. Use whenever writing TypeScript specs or tests, creating spec files/folders, using the…
write-specs-frontend
Use this skill to write specs for the React/TypeScript surface of a Cratis APPLICATION slice — view models, helpers, and component behavior (Vitest + Mocha-style describe/it + Sinon + Chai .should). The frontend peer to write-specs (backend). For framework @cratis/ package specs use cratis-specs-typescript instead.