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/chordee/houdini-tools/houdini-node-helpnpx skills add chordee/houdini-tools --skill houdini-node-helpgit clone --depth 1 https://github.com/chordee/houdini-toolsWrote 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/chordee/houdini-tools/houdini-node-help)<a href="https://agentmods.dev/skills/chordee/houdini-tools/houdini-node-help"><img src="https://agentmods.dev/badge/skills/chordee/houdini-tools/houdini-node-help.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 | $0.00075 | $0.01910 |
| Opus 5 | $0.00037 | $0.00955 |
| Sonnet 5 | $0.00015 | $0.00382 |
| Haiku 4.5 | $0.00007 | $0.00191 |
Grade A, and why
houdini-node-help 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 5d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Houdini node help
Houdini node help is not Markdown. It is Houdini's own wiki markup, and the authoritative reference ships with every install — along with 5000+ real examples. Read those before writing.
Read the shipped docs first
An agent asked to write node help will usually produce something close to correct from memory, and get the details wrong in ways that break rendering. The details are cheap to look up:
# H is the Houdini install root — the directory holding bin/ and houdini/,
# which is what $HFS points at. Not the path to hython.
H="$HFS" # e.g. D:/Programs/Side Effects Software/Houdini 22.0.368
# Node help specifics: where it goes, file naming, page structure (473 lines)
python -c "import zipfile;print(zipfile.ZipFile(r'$H/houdini/help/help.zip').read('nodes.txt').decode('utf-8','replace'))"
# Full wiki markup reference (1469 lines)
python -c "import zipfile;print(zipfile.ZipFile(r'$H/houdini/help/help.zip').read('format.txt').decode('utf-8','replace'))"
# A real example from the SAME context as your node: sop/, lop/, dop/, cop/, ...
EXAMPLE="sop/scatter.txt"
python -c "import zipfile;print(zipfile.ZipFile(r'$H/houdini/help/nodes.zip').read('$EXAMPLE').decode('utf-8','replace'))"
Without a local install, the same two documents are online, and so is every node example:
- Documenting your assets — the online
nodes.txt, including a style-tips section on writing parameter descriptions that say something - Wiki markup reference — the online
format.txt - Any node's page, e.g. sop/scatter
The .txt trick from format.txt — appending .txt to a help URL to see its raw markup — works on the help server Houdini runs locally, not on sidefx.com, where it 404s. For raw markup without a running help server, read nodes.zip as above.
Prefer the local copies when Houdini is installed — they match the version being authored against, and the online docs track the current release.
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.
- 5d ago First seen · 146 lines · 75 tokens per session scan A 73863b83e951
houdini-node-help is a skill published in the GitHub repository chordee/houdini-tools (5 stars, last pushed 6d ago), licensed MIT. It adds 75 tokens to every session and 1,910 once invoked, about $0.0004 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
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
统一创建、改写、品牌化或忠实转载微信公众号文章包：正文写作调用唯一文风与作者性能力，离线完成结构、品牌、封面、4:3 首图、来源与质量验收。Use when asked to write, brand, audit, or faithfully repost a WeChat article package.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…