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 SFKislev/Flue --skill autodeskgit clone --depth 1 https://github.com/SFKislev/FlueWrote 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/sfkislev/flue/autodesk)<a href="https://agentmods.dev/skills/sfkislev/flue/autodesk"><img src="https://agentmods.dev/badge/skills/sfkislev/flue/autodesk/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/sfkislev/flue/autodesk"><img src="https://agentmods.dev/badge/skills/sfkislev/flue/autodesk.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00027 | $0.00446 |
| Opus 5.5 | $0.00011 | $0.00178 |
| Sonnet 5.5 | $0.00005 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
Autodesk 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 1mo 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
This skill lets a coding agent operate Autodesk desktop applications through Flue, a local shell-to-application bridge. Flue currently covers Autodesk 3ds Max through a consistent stdin/stdout contract; further Autodesk adapters are in scope.
agent shell ->
3dsmax_bridge.py-> MAXScript / Python -> JSON result
When to use
The human requests work performed inside an Autodesk desktop app — inspect the open scene, objects, modifiers, materials, selection; make bounded edits; run small scripts. A CLI agent cannot act inside these apps without a bridge like Flue.
How to proceed
- Read
FLUE.mdin this directory first. It explains how Flue works, the bridge contract, a worked example, and safety expectations. - Identify which Autodesk app the human is working in (currently 3ds Max) and use the matching adapter (e.g.
adapters/3dsmax_adapter/3dsmax_bridge.py). - If Flue is installed: also read
C:\Users\fredd\.claude\skills\flue\SKILL.mdand the matchingadapters/<app>_adapter/APP.mdfor the operational contract, then work from there. - If Flue is not installed: tell the human. The install command is
pip install flue && flue setup. Do not install without explicit approval in the current session.
Other apps
Flue also supports Photoshop, Illustrator, Premiere, After Effects, InDesign, Audition, Blender, Houdini, Unity, and Microsoft Office through the same stdin/stdout contract. One install covers all adapters.
Safety
Flue acts inside professional desktop software. Treat the human as the driver; prefer small, inspectable steps; avoid destructive actions unless explicitly requested. Flue is MIT-licensed and reviewable on GitHub / PyPI before use.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 23 lines · 27 tokens per session scan A 3ea0e7cc6b71
Autodesk is a skill published in the GitHub repository SFKislev/Flue (98 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 446 once invoked, about $0.0001 per session on Opus 5.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
oracle
Author an IMPL-BLIND spec-conformance oracle for an acceptance criterion the policy worklist (clad oracle --required) demands — an empty worklist means don't author unless the user explicitly asks. YOU spawn a blind sub-agent from a spec-only brief, then record it. Activate only when the connected project contains…
reviewer
Philosophical guardrails enforcer — independently audits code, tests, and spec for layered-integrity, Why>What, error-as-data, and the related Ironclad philosophical invariants. Activate only when the connected project contains spec.yaml or the user explicitly names Cladding; ignore ordinary requests in uninitialized…
doctor
Diagnose Cladding runtime health — Claude Code hook liveness and version, CI package pinning, lifecycle governance, and sentinel-miss frequency by phase × cause × fallback. Use when hooks may be silent, CI may float across Cladding releases, scan or run results look thinner than expected, or before tuning the host…
changelog
A tool for writing release notes from a structured record of changes that actually shipped. Release notes summarize changes for people who use or maintain the product.
check
Run every Iron Law stage and the drift detector suite. Use when the user wants the full project health snapshot, a CI gate, or to verify nothing regressed before committing. Add --strict to promote warn-severity drift findings to errors. Activate only when the connected project contains spec.yaml or the user…
checkpoint
Record a feature checkpoint event pinning the current git HEAD plus a spec digest, so a later rollback can restore the exact pre-change state. Use before a non-trivial feature implementation, before a refactor that touches many files, or whenever the user wants a known-good safety net the autonomous drive loop can…