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 hybridlabor-api/bdb-dev-optimized-agent-skills --skill td-feature-qagit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/td-feature-qa)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/td-feature-qa"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/td-feature-qa/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/hybridlabor-api/bdb-dev-optimized-agent-skills/td-feature-qa"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/td-feature-qa.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.00105 | $0.01006 |
| Opus 5 | $0.00053 | $0.00503 |
| Sonnet 5 | $0.00021 | $0.00201 |
| Haiku 4.5 | $0.00011 | $0.00101 |
Grade A, and why
td-feature-qa 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 9d 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.
This is a copy
91% identical to td-feature-qa — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
td-feature-qa — verify it works, not just exists
Most defects here live at boundaries, and a tool that returns success can still cook to errors or a black frame. So: read both sides of every boundary together, and check errors after the network cooks, not just the create_* return flag. Run incrementally — validate each feature as it lands so an early boundary bug doesn't propagate.
Gates + suites — always run (offline, no TD needed)
npm run typecheck·npm run build·npm test- biome via
./node_modules/.bin/biome check .(NOTnpm run lint— RTK proxy gives a false ESLint parse error) npm run validate:recipes·npm run test:bridge(python3 -m unittest discover -s td/tests)
Cross-boundary checks — open both sides
| Boundary | Left (producer) | Right (consumer) | Compare |
|---|---|---|---|
| Tool ↔ CLI | tool's Zod inputSchema |
command in src/cli/agent.ts |
every param reachable from CLI; types/defaults align; name maps to the right handler |
| Tool ↔ registry | register… export |
layer*/index.ts + tools/index.ts |
actually registered + aggregated, not just written |
| Tool ↔ docs | live registry | generated docs/reference/tools.md |
regenerates and includes the new tool |
…Impl ↔ test |
real return / isError shape |
msw test assertions | test exercises the actual shape, not a cast-away generic |
| Code ↔ TD | operator types created | what this build can create | optype exists + is createable (dir(td) suffix-match over-counts; ~22 names not createable; KB lags ~14 ops) |
| Bridge ↔ client | td/ endpoint/payload |
touchDesignerClient.ts + validators.ts envelope |
response shape matches the Zod validator |
Live TD validation — when the bridge is up
Policy: offline gates always; live when available. Call get_td_info first.
- Bridge up: build the feature through the agent CLI against the live bridge, capture
get_preview, and checkget_td_node_errorsafter it cooks. - Bridge offline: run offline gates, mark live validation UNVERIFIED — pending bridge in the report. Do not fail the pipeline for a missing TD.
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.
- 9d ago First seen · 49 lines · 105 tokens per session scan A 1dc5540176fe
td-feature-qa is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 105 tokens to every session and 1,006 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to td-feature-qa, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.
eval-harness
Evaluation harness for testing agent and skill quality through structured benchmarks, regression tests, and quality scoring.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.