Borrowing it
Nothing to install: this file belongs to 8beeeaaat/touchdesigner-mcp. 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/8beeeaaat/touchdesigner-mcp/main/.claude/skills/integration-test-guard/SKILL.mdgit clone --depth 1 https://github.com/8beeeaaat/touchdesigner-mcpWrote 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/8beeeaaat/touchdesigner-mcp/integration-test-guard)<a href="https://agentmods.dev/skills/8beeeaaat/touchdesigner-mcp/integration-test-guard"><img src="https://agentmods.dev/badge/skills/8beeeaaat/touchdesigner-mcp/integration-test-guard.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 MCP Rug Pull · line 56 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 57 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 62 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.00135 | $0.01095 |
| Opus 5 | $0.00068 | $0.00548 |
| Sonnet 5 | $0.00027 | $0.00219 |
| Haiku 4.5 | $0.00014 | $0.00110 |
Grade A, and why
integration-test-guard 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- integration-test-guard — 88% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Test Guard
When you change the MCP server / API surface, add or update a test in
tests/integration/ or tests/e2e/. The integration-test-guard hook blocks
git push when the outgoing commits touch API/MCP source without one (override
with SKIP_ITEST_GUARD=1 only when a test genuinely does not apply).
What counts as "API/MCP surface"
src/api/** (OpenAPI schema) · src/features/tools/** (tool defs + handlers) ·
src/server/** (MCP server) · src/tdClient/** (TD HTTP client) ·
src/transport/** (stdio/HTTP transport) · td/modules/mcp/** (TD-side Python API).
Step 1 — pick the right suite (by what the change affects)
| Change affects | Suite | Needs live TD (9981)? |
|---|---|---|
| MCP tool response shape / formatting, tool registration, manifest | tests/integration/mcpToolsResponse.test.ts |
No — uses server.getTool(...) with mocked client |
| Client ↔ WebServer behavior (create/update/delete/exec, TD-side Python) | tests/integration/touchDesignerClientAndWebServer.test.ts |
Yes — real TouchDesignerClient over HTTP |
HTTP transport (stateless /mcp serving, /health) |
tests/integration/httpTransport.test.ts |
No live TD, but starts the HTTP server |
Protocol-era behavior of the built CLI (2026-07-28 negotiation via server/discover, 2025-era fallback, serveStdio / createMcpHandler wiring, CLI args) |
tests/e2e/*.e2e.test.ts |
No — spawns dist/cli.js, drives it with the real MCP SDK client |
If the change spans two categories, cover each in its suite.
Step 2 — add / update the test
Follow the existing patterns in the chosen file:
- mcpToolsResponse: get the tool via
server.getTool(TOOL_NAMES.X), invoke its handler with a mocked TD client, assert the formatted response shape. - touchDesignerClientAndWebServer: use the shared
tdClientand thetest_base_compsandbox (created inbeforeAll); exercise the real call path, then reconcile against a runtime value (read it back and compare) rather than trusting the response alone. Clean up created nodes.
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 · 82 lines · 135 tokens per session scan A cc76d4587475
integration-test-guard is a skill published in the GitHub repository 8beeeaaat/touchdesigner-mcp (519 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 1,095 once invoked, about $0.0007 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
coding-agents-hooks-authoring
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
data-collection
To gather QA source artifacts from issue tracker, wiki, test management system.
workshop-testing
Walk through the .NET AI Workshop as an attendee to validate that the READMEs, commands, and code snapshots still work. USE FOR: testing the workshop, testing a specific Part, dry-running the labs, verifying a README against its snapshot, reconciling or refreshing code snapshots, producing a workshop test report. DO…
frontmcp-testing
Use for anything about testing FrontMCP servers: writing or running unit, integration, and E2E tests and reaching the 95%+ coverage bar. Covers Jest setup and coverage gating; unit-testing a ToolContext execute() with mock context, inputs, and Zod schema validation; testing resources and prompts; in-memory testing via…
build-swiftui-interface
Use when a coding agent must design, scaffold, implement, or verify an iOS or macOS SwiftUI interface with Apple-platform state, accessibility, availability, testing, and Xcode evidence.