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/jacobinwwey/notemdpro/test-driven-developmentnpx skills add Jacobinwwey/notemdpro --skill test-driven-developmentgit clone --depth 1 https://github.com/Jacobinwwey/notemdproWhat 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 | $0.00031 | $0.00703 |
| Opus 5 | $0.00015 | $0.00351 |
| Sonnet 5 | $0.00006 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
test-driven-development 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoteMD Pro - Testing & Regression Defense
Overview
The obsidian-NoteMD_new source project contains a robust suite of 35 Jest unit tests located in the src/tests/ directory. When acting as an AI Agent modifying core utilities, heuristic engines, or batch processors within this skill set, you MUST engage this testing framework to prevent regressions.
🛡️ The Prime Directive
[!CAUTION] Mandatory Regression Testing If you modify
fileUtils.ts,mermaidProcessor.ts,formulaFixer.ts, or any other core utility, you are required to run the local test suite and ensure all 35 mocked tests pass. Do not present a "completed" refactor to the user without terminal proof thatnpm testsucceeded.
Test Suite Structure
The tests are located in src/tests/ and use Obsidian-specific mocks (src/__mocks__/):
| Test File | Responsibilities |
|---|---|
mermaidDeepDebug.test.ts |
Validates complex Mermaid structural repairs |
mermaidFix*.test.ts |
15+ individual files testing specific Mermaid regex fixes (e.g., arrows, quotes, semicolons) |
conceptNoteCreation.test.ts |
Tests the createConceptNotes logic and de-duplication |
formulaCorrection.test.ts |
Validates the LaTeX delimiter $..$ conversions |
parallelBatch.test.ts |
Tests concurrency control and processor limits |
processFile.test.ts |
End-to-end testing of the wiki-link processing pipeline |
Executing Tests
To run the full suite:
npm run test
To run a specific test file when iterating on a feature:
npm run test -- mermaidDeepDebug.test.ts
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.
- 2d ago First seen · 77 lines · 31 tokens per session scan A b9beb6d86d94
test-driven-development is a skill published in the GitHub repository Jacobinwwey/notemdpro (2 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 703 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-31.
Other skills, from other repositories
testing
Applies repository-aware TDD, observable test design, and applicable quality checks. Use when changing behavior, writing tests, or reviewing test quality.
Test Driven Development
Strict Red-Green-Refactor implementation methodology for high quality, regression-free software.
tdd
Use this skill to practice test-driven development — writing tests before implementation, using tests to drive design, and validating implementation against pre-written tests. Activates when implementing new functionality, refactoring code, or fixing bugs where regression coverage is needed.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
test-driven-development
在实现任何功能或修复 bug 时使用，在编写实现代码之前.
engineering-workflow
可靠工程工作流的执行细则——探索→计划→TDD→系统化调试→代码审查→完成前验证。供方法论教练在开发任务中逐步引导。.