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 skills add kimimgo/viznoir --skill dev-pipelinegit clone --depth 1 https://github.com/kimimgo/viznoirWrote 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/kimimgo/viznoir/dev-pipeline)<a href="https://agentmods.dev/skills/kimimgo/viznoir/dev-pipeline"><img src="https://agentmods.dev/badge/skills/kimimgo/viznoir/dev-pipeline/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/kimimgo/viznoir/dev-pipeline"><img src="https://agentmods.dev/badge/skills/kimimgo/viznoir/dev-pipeline.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.00068 | $0.00376 |
| Opus 5 | $0.00034 | $0.00188 |
| Sonnet 5 | $0.00014 | $0.00075 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
dev-pipeline 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 8d 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
viznoir Dev Pipeline
Workflow
Issue → Explore → Plan → TDD (Red→Green→Refactor) → Benchmark → PR → Review
viznoir-Specific Checklist
New Filter
- Register in
core/registry.py(PascalCase key, VTK class + param schema) - Register in
engine/filters.py(snake_case key, VTK filter function) - Add to
TOOL_DISPATCHinharness/orchestrator.pyif image-producing - Test in
tests/test_engine/test_filters.py
New Tool
- Create
tools/{name}.pywith{name}_impl()function - Register
@mcp.tool()inserver.py - Test in
tests/test_tools/ - Add to
TOOL_DISPATCHif image-producing
VTK Rendering Test
- Name file
*_vtk.py(auto-skipped in CI) OR - Add to
conftest.pyskip list
Benchmark
- Write
bench_*.pyfollowingbench_comparison.pypattern - Update
REPORT.mdwith results
PR Quality Gate
- Test count >= CI guard (currently 1430)
- Coverage >= 80%
ruff check src/ tests/cleanmypy src/viznoir/clean
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.
- 8d ago First seen · 42 lines · 68 tokens per session scan A e7f9f4670fdd
dev-pipeline is a skill published in the GitHub repository kimimgo/viznoir (17 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 376 once invoked, about $0.0003 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
implement
Implement a specification using a TDD-oriented workflow. Extracts requirements, generates tests first, then implements to pass the tests. Includes spiral detection and acceptance gates.
prespec
Write the behaviour specification for a feature BEFORE implementing it, as test cases. Use whenever you are about to build a new endpoint, screen, flow, or behaviour — especially anything touching auth, sessions, tokens, lists, or pagination. Also use when asked "how should I test this", "what should this actually…
Test Driven Development
Strict Red-Green-Refactor implementation methodology for high quality, regression-free software.
testing
Comprehensive software testing skill covering unit tests, integration tests, TDD/BDD, mocking strategies, and test automation across multiple languages. Use this skill when writing test cases, designing test strategies, implementing test automation, or need guidance on testing frameworks and best practices. Ideal for…
tdd
Use test-driven development for behavior-changing feature or fix work, and whenever the user mentions TDD, test-first, red-green-refactor, tracer bullets, integration tests, or public-interface behavior tests. Skip for docs-only, path-only rename, formatting-only, or purely mechanical chores unless explicitly…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.