modelopt-deployment
Skill5.6k starsChanged todayApache-2.0View on GitHub
Serve a quantized or unquantized LLM checkpoint as an OpenAI-compatible API endpoint using vLLM, SGLang, or TRT-LLM. Use when user says "deploy model", "serve model", "start vLLM server", "launch SGLang", "TRT-LLM deploy", "AutoDeploy", "benchmark throughput", "serve checkpoint", or needs an inference endpoint from a HuggingFace or ModelOpt-quantized checkpoint. Do NOT use for quantizing models (use modelopt-ptq) or evaluating accuracy (use modelopt-evaluation).
1 other project uses a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- NVIDIA/Model-Optimizerword for word, first seen Nov 15, 2026
Who's talking about NVIDIA/TensorRT-Model-Optimizer
- NVIDIA/Model-Optimizer“Replace ONNX simplification package from onnxsim to onnxslim”GitHub · Oct 28, 2025 · 1 reactions
- NVIDIA/Model-Optimizer“Fix FLOPs calculation”GitHub · Sep 29, 2025 · 1 reactions
- NVIDIA/Model-Optimizer“[Autocast] Fix edge case casting input directly to output”GitHub · Sep 9, 2025 · 1 reactions
- NVIDIA/Model-Optimizer“[Autocast] Fix edge case with cast producing network output”GitHub · Sep 8, 2025 · 1 reactions
- NVIDIA/Model-Optimizer“"Unknown quantization method" when loading nvfp4 checkpoint with vLLM”GitHub · Aug 19, 2025 · 1 reactions
The biggest 5 of 45 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 45
Talked about on GitHub (45 times).
On GitHub · 45
- Oct 28, 2025Replace ONNX simplification package from onnxsim to onnxslim — NVIDIA/Model-Optimizer1 reaction · 23 comments
- Sep 29, 2025Fix FLOPs calculation — NVIDIA/Model-Optimizer1 reaction · 11 comments
- Sep 9, 2025[Autocast] Fix edge case casting input directly to output — NVIDIA/Model-Optimizer1 reaction · 10 comments
- Sep 8, 2025[Autocast] Fix edge case with cast producing network output — NVIDIA/Model-Optimizer1 reaction · 6 comments
- Aug 19, 2025"Unknown quantization method" when loading nvfp4 checkpoint with vLLM — NVIDIA/Model-Optimizer1 reaction · 3 comments
40 more on GitHub
- Mar 30, 2025[Quantization] Add TRT-ModelOpt as a Backend — huggingface/diffusers1 reaction · 50 comments
- Mar 11, 2025✨[Feature] Supporting Blackwell FP4 — pytorch/TensorRT1 reaction
- Sep 16, 2026推論最適化ツール・OSS — warabinbin/papers0 reactions
- Aug 10, 2026fold_weight crashes with AttributeError: 'NoneType' object has no attribute 'data' on Megatron models with tied word embeddings — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Dec 5, 2025Kimi-k2 calib+export — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Dec 4, 2025Quantization — HashCitrine/sample-to-make-llm-service0 reactions
- Dec 4, 2025Diffusion Rename [TRT MO -> MO] — NVIDIA/Model-Optimizer0 reactions · 2 comments
- Dec 3, 2025[5704162] Create a copy to avoid leaking ProcessGroup into state dict — NVIDIA/Model-Optimizer0 reactions · 6 comments
- Dec 2, 2025fix: Fix auto quantize multi-gpu tests — NVIDIA/Model-Optimizer0 reactions · 3 comments
- Dec 2, 2025qwen3_8b eagle3 model train and vllm ckpt export — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 27, 2025Add all example e2e tests for github PR merge / nightly — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 26, 2025[Bug Fix]: Correct block_size in NVFP4_MLP_WEIGHT_ONLY_CFG to support vLLM inference — NVIDIA/Model-Optimizer0 reactions · 3 comments
- Nov 26, 2025fix: relax sympy version — inisis/OnnxSlim0 reactions · 1 comment
- Nov 24, 2025[None][doc] Deprecate --export_fmt flag when using ModelOpt — NVIDIA/TensorRT-LLM0 reactions · 4 comments
- Nov 24, 2025[Help wanted] CNN QAT: How to correctly export ONNX and use DeviceModel for inference — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 22, 2025fix: issues related to TensorRT-Model-Optimizer — inisis/OnnxSlim0 reactions · 2 comments
- Nov 20, 2025[2/N] Added KDLoss based AutoQuantize — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 20, 2025[1/N] Refactored AutoQuantizeSearcher to _AutoQuantizeBaseSearcher & AutoQuantizeGradientSearcher; seperated quant modules and score modules — NVIDIA/Model-Optimizer0 reactions · 11 comments
- Nov 17, 2025failed to quant the Qwen3-VL-30B-A3B — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 13, 2025Support Wan2.2 t2v diffusers quantization — NVIDIA/Model-Optimizer0 reactions · 3 comments
- Nov 3, 2025PyTorch geometric quantization support — NVIDIA/Model-Optimizer0 reactions · 1 comment
- Nov 3, 2025Failed to save quantized model if some tensors offload to CPU — NVIDIA/Model-Optimizer0 reactions · 2 comments
- Oct 28, 2025[OMNIML-2917] export layer config using actual prefix instead of hard… — NVIDIA/Model-Optimizer0 reactions · 9 comments
- Oct 27, 2025Add convert_llama3_config_to_decilm_config + unit test — NVIDIA/Model-Optimizer0 reactions · 2 comments
- Sep 25, 2025CodeRabbit Generated Unit Tests: Add GPU tests for Megatron quantization; review/refactor unit tests — NVIDIA/Model-Optimizer0 reactions · 2 comments
- Sep 25, 2025📝 Add docstrings to `kaix/kvcache_mcore` — NVIDIA/Model-Optimizer0 reactions · 2 comments
- Sep 15, 2025FP8 Block quantize onnx export support — NVIDIA/Model-Optimizer0 reactions · 3 comments
- Sep 15, 2025add end_process in deepseek ptq — NVIDIA/Model-Optimizer0 reactions · 10 comments
- Jul 13, 2025feat: Simplify and Improve Whisper Example — NVIDIA/TensorRT-LLM0 reactions · 3 comments
- Jul 3, 2025[future request] Support more quant for torch backend — NVIDIA/TensorRT-LLM0 reactions · 2 comments
- Jul 3, 2025🐛 [Bug] examples/dynamo/torch_compile_gpt2.py run failed — pytorch/TensorRT0 reactions · 2 comments
- Jun 15, 2025INT8 to FP8 scale conversion — NVIDIA/Model-Optimizer0 reactions · 6 comments
- Jun 13, 2025Fix speculative decoding example — NVIDIA/Model-Optimizer0 reactions · 6 comments
- May 21, 2025`get_modelike_from_algo_cfg` doesn't accept `QuantizeAlgorithmConfig`, but it's typing says it should — NVIDIA/Model-Optimizer0 reactions · 3 comments
- May 17, 2025Decode latency of FP4 LLM is higher than expected — NVIDIA/TensorRT-LLM0 reactions · 1 comment
- May 7, 2025Error in torch_compile.ipynb — Project-MONAI/tutorials0 reactions · 1 comment
- May 6, 2025当我使用增量训练的时候,只改变修改一个feature的zch_size的大小,其他所有配置都不改变,会出错。 — alibaba/TorchEasyRec0 reactions
- Apr 30, 2025INT8 quantization for HiFi-GAN vocoder -- performance issue — NVIDIA/TensorRT0 reactions · 7 comments
- Mar 24, 2025bert model split into many layers after int8 quantization — NVIDIA/TensorRT0 reactions · 13 comments
- Sep 8, 2024urlopen error retrieval incomplete in modules/autoencoder_mednist.ipynb — Project-MONAI/tutorials0 reactions
Other versions1 project uses a version of this.
Word for word · 1
- NVIDIA/Model-Optimizer★ 5.6k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- tools/debugger/CLAUDE.mdCLAUDE.md
- tools/launcher/CLAUDE.mdCLAUDE.md
- accessing-mlflowSkill
- benchmark-model-kernelsSkill
- commonSkill
- compare-resultsSkill
- day0-releaseSkill
- debugSkill
- deploymentSkill
- evaluationSkill
- launching-evalsSkill
- modelopt-accessing-mlflowSkill
- modelopt-benchmark-model-kernelsSkill
- modelopt-compare-resultsSkill
- modelopt-day0-releaseSkill
- modelopt-debugSkill
- modelopt-evaluationSkill
- modelopt-launching-evalsSkill
- modelopt-monitorSkill
- modelopt-ptqSkill
- modelopt-qadSkill
- modelopt-quant-recipe-searchSkill
- modelopt-release-cherry-pickSkill
- modelopt-run-agentxSkill
- modelopt-speculative-decodingSkill
- monitorSkill
- ptqSkill
- qadSkill
- quant-recipe-searchSkill
- release-cherry-pickSkill
- run-agentxSkill
- speculative-decodingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. About 0 are common, 9 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Prefer $SKILL_DIR/scripts/deploy.sh for standard local deployments — it handles quant detection, health checks, and server lifecycle.
- Very specific: line 41
If MODELOPT_WORKSPACE_ROOT is set, use the common skill's workspace-management.md.
- Very specific: line 47
If the user says "deploy the model I just quantized" or references a previous PTQ, find the matching workspace and cd into it.
- Distinctive: line 59
Check the quantization format if applicable:
- Very specific: line 65
If not found, also check config.json for a quantization_config section with quant_method: "modelopt".
- Distinctive: line 69
If the user hasn't specified a framework, recommend based on this priority:
- Very specific: line 78
Check the support matrix in references/support-matrix.md to confirm the model + format + framework combination is supported.
- Very specific: line 82
Use the common skill's environment-setup.md for GPU detection, local vs remote, and SLURM/Docker/bare metal detection.
- Very specific: line 92
If not installed, consult references/setup.md.
- Distinctive: line 99
Add ~2-4 GB for KV cache and framework overhead
- Very specific: line 101
If the model exceeds single GPU memory, use tensor parallelism (-tp <num_gpus>).
- Distinctive: line 105
Read the framework-specific reference for detailed instructions:
- Distinctive: line 181
After the server starts, verify it's healthy:
- Distinctive: line 200
All checks must pass before reporting success to the user.
- Distinctive: line 204
If the user asks to benchmark, measure throughput/latency, or compare precisions, use AIPerf (Apache-2.0, OpenAI-compatible client …
- Very specific: line 212
If a cluster config exists (~/.config/modelopt/clusters.yaml, .agents/clusters.yaml, or .claude/clusters.yaml), or the user mentions …
- Very specific: line 228
If the checkpoint path is a remote/absolute path (e.g., from a prior PTQ run on the cluster), skip sync — it's already there.
- Distinctive: line 274
Test generation produces coherent output
- Distinctive: line 276
If benchmarking was requested, throughput/latency numbers are reported
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Deployment Skill
Serve a model checkpoint as an OpenAI-compatible inference endpoint. Supports vLLM, SGLang, and TRT-LLM (including AutoDeploy).
Quick Start
Prefer $SKILL_DIR/scripts/deploy.sh for standard local deployments — it handles quant detection, health checks, and server lifecycle. Use the raw framework commands in Step 4 when you need flags the script doesn't support, or for remote deployment.
# Start vLLM server with a ModelOpt checkpoint
"$SKILL_DIR/scripts/deploy.sh" start --model ./qwen3-0.6b-fp8
# Start with SGLang and tensor parallelism
"$SKILL_DIR/scripts/deploy.sh" start --model ./llama-70b-nvfp4 --framework sglang --tp 4
# Start from HuggingFace hub
"$SKILL_DIR/scripts/deploy.sh" start --model nvidia/Llama-3.1-8B-Instruct-FP8
# Test the API
"$SKILL_DIR/scripts/deploy.sh" test
# Check status
"$SKILL_DIR/scripts/deploy.sh" status
# Stop
"$SKILL_DIR/scripts/deploy.sh" stopThe script handles: GPU detection, quantization flag auto-detection (FP8 vs FP4), server lifecycle (start/stop/restart/status), health check polling, and API testing.
Decision Flow
0. Check workspace (multi-user / Slack bot)
If MODELOPT_WORKSPACE_ROOT is set, use the common skill's workspace-management.md. Before creating a new workspace, check the current session for existing model workspaces — especially if deploying a checkpoint from a prior PTQ run:
ls "$MODELOPT_WORKSPACE_ROOT/<session_id>/" 2>/dev/nullIf the user says "deploy the model I just quantized" or references a previous PTQ, find the matching workspace and cd into it. The checkpoint should be in that workspace's output directory.
1. Identify the checkpoint
Determine what the user wants to deploy:
- Local quantized checkpoint (from ptq skill or manual export): look for
hf_quant_config.jsonin the directory. If coming from a prior PTQ run in the same workspace, check common output locations:output/,outputs/,exported_model/, or the--export_pathused in the PTQ command. - HuggingFace model hub (e.g.,
nvidia/Llama-3.1-8B-Instruct-FP8): use directly - Unquantized model: deploy as-is (BF16) or suggest quantizing first with the ptq skill
Note: This skill expects HF-format checkpoints (from PTQ with
--export_fmt hf). TRT-LLM format checkpoints should be deployed directly with TRT-LLM — seereferences/trtllm.md.
Check the quantization format if applicable:
cat <checkpoint_path>/hf_quant_config.json 2>/dev/null || echo "No hf_quant_config.json"If not found, also check config.json for a quantization_config section with quant_method: "modelopt". If neither exists, the checkpoint is unquantized.
2. Choose the framework
If the user hasn't specified a framework, recommend based on this priority:
| Situation | Recommended | Why |
| General use | vLLM | Widest ecosystem, easy setup, OpenAI-compatible |
| Best SGLang model support | SGLang | Strong DeepSeek/Llama 4 support |
| Maximum optimization | TRT-LLM | Best throughput via engine compilation |
| Mixed-precision / AutoQuant | TRT-LLM AutoDeploy | Only option for AutoQuant checkpoints |
Check the support matrix in references/support-matrix.md to confirm the model + format + framework combination is supported.
3. Check the environment
Use the common skill's environment-setup.md for GPU detection, local vs remote, and SLURM/Docker/bare metal detection. After completing it you should know: GPU model/count, local or remote, and execution environment.
Then check the deployment framework is installed:
python -c "import vllm; print(f'vLLM {vllm.__version__}')" 2>/dev/null || echo "vLLM not installed"
python -c "import sglang; print(f'SGLang {sglang.__version__}')" 2>/dev/null || echo "SGLang not installed"
python -c "import tensorrt_llm; print(f'TRT-LLM {tensorrt_llm.__version__}')" 2>/dev/null || echo "TRT-LLM not installed"If not installed, consult references/setup.md.
GPU memory estimate (to determine tensor parallelism):
- BF16:
params × 2 bytes(8B ≈ 16 GB) - FP8:
params × 1 byte(8B ≈ 8 GB) - FP4:
params × 0.5 bytes(8B ≈ 4 GB) - Add ~2-4 GB for KV cache and framework overhead
If the model exceeds single GPU memory, use tensor parallelism (-tp <num_gpus>).
4. Deploy
Read the framework-specific reference for detailed instructions:
| Framework | Reference file |
| vLLM | references/vllm.md |
| SGLang | references/sglang.md |
| TRT-LLM | references/trtllm.md |
Quick-start commands (for common cases):
vLLM
# Serve as OpenAI-compatible endpoint
python -m vllm.entrypoints.openai.api_server \
--model <checkpoint_path> \
--quantization modelopt \
--tensor-parallel-size <num_gpus> \
--host 0.0.0.0 --port 8000For NVFP4 checkpoints, use --quantization modelopt_fp4.
NVFP4 on Blackwell B300/GB300 (sm_103) needs a CUDA-13 image. From v0.20.0 on, release tags are CUDA-13 unsuffixed (e.g.
vllm/vllm-openai:v0.26.0) with-cu129the CUDA-12 opt-out; v0.19.x and earlier were the other way round (-cu130= CUDA 13), and-cu130no longer exists after v0.20.0. Don't trust the tag name — select a tag reportingCUDA_VERSION>= 13 in the config blob of your platform's child manifest (arm64 Grace/GB300, amd64 x86);TORCH_CUDA_ARCH_LISTdiffers between the two. A cu12 build has no sm_103 FP4 kernel, so vLLM loads the checkpoint then dies at engine init withCUDA error: no kernel image is available for execution on the device(affects theflashinferandcutlassNVFP4 backends;marlinseparately fails on non-64-divisible layer dims). Cross-check viarecipes.vllm.ai/<org>/<model>?hardware=b300(JS-rendered — fetch the raw markdown atgithub.com/vllm-project/recipes/blob/main/<org>/<model>.md). For multimodal models on sm_103, also pass--mm-encoder-attn-backend TRITON_ATTN(the default CuTe ViT flash-attn asserts "Only SM 10.x and 11.x").
SGLang
python -m sglang.launch_server \
--model-path <checkpoint_path> \
--quantization modelopt \
--tp <num_gpus> \
--host 0.0.0.0 --port 8000For NVFP4 checkpoints, use --quantization modelopt_fp4.
Cross-check SGLang launch flags via the SGLang cookbook (the SGLang analog of
recipes.vllm.ai):docs.sglang.io/cookbook/<category>/<org>/<model>(e.g..../autoregressive/DeepSeek/DeepSeek-V4) — authoritative for parallelism, MoE backends, strategy flags, Docker image, and min version. Select the variant via the URL fragment#hw=...&variant=...&quant=...&strategy=...&nodes=.... The page is JS-rendered — fetch the raw markdown atraw.githubusercontent.com/sgl-project/sglang/main/docs_new/cookbook/<category>/<org>/<model>.mdx. SM120 (RTX PRO 6000) needs thelmsysorg/sglang:devnightly (:latestlacks SM120). Seereferences/sglang.mdfor the full backend/flag matrix.
TRT-LLM (direct)
from tensorrt_llm import LLM, SamplingParams
llm = LLM(model="<checkpoint_path>")
outputs = llm.generate(["Hello, my name is"], SamplingParams(temperature=0.8, top_p=0.95))TRT-LLM AutoDeploy
For AutoQuant or mixed-precision checkpoints, see references/trtllm.md.
5. Verify the deployment
After the server starts, verify it's healthy:
# Health check
curl -s http://localhost:8000/health
# List models
curl -s http://localhost:8000/v1/models | python -m json.tool
# Test generation
curl -s http://localhost:8000/v1/completions \
-H "Content-Type: application/json" \
-d '{
"model": "<model_name>",
"prompt": "The capital of France is",
"max_tokens": 32
}' | python -m json.toolAll checks must pass before reporting success to the user.
5b. Benchmark throughput/latency (optional)
If the user asks to benchmark, measure throughput/latency, or compare precisions,
use AIPerf (Apache-2.0, OpenAI-compatible client benchmark). See
references/benchmarking.md for install, the pre-benchmark coherence gate, the
aiperf profile flags (notably --extra-inputs ignore_eos:true), suggested
token shapes, and how to read profile_export_aiperf.json.
6. Remote deployment (SSH/SLURM)
If a cluster config exists (~/.config/modelopt/clusters.yaml, .agents/clusters.yaml, or .claude/clusters.yaml), or the user mentions running on a remote machine:
- Check container registry auth — before submitting any SLURM job with a container image, verify credentials exist on the cluster per the common skill's
slurm-setup.mdsection 6. If credentials are missing for the image's registry, ask the user to fix auth or switch to an image on an authenticated registry (e.g., NGC). Do not submit until auth is confirmed. Source remote utilities: Load the common skill, then resolve
remote_exec.shfrom that skill's root.source "<common-skill-dir>/remote_exec.sh" remote_load_cluster remote_check_ssh remote_detect_envSync the checkpoint (only if it was produced locally):
If the checkpoint path is a remote/absolute path (e.g., from a prior PTQ run on the cluster), skip sync — it's already there. Verify with
remote_run "ls <checkpoint_path>/config.json". Only sync if the checkpoint is local:remote_sync_to <local_checkpoint_path> <session_id>/<model>/checkpoints/Deploy based on remote environment:
- SLURM — see the common skill's
slurm-setup.mdfor job script templates (container setup, account/partition discovery). The server command inside the container is the same as Step 4 (e.g.,python -m vllm.entrypoints.openai.api_server --model <path> --quantization modelopt). After submitting, register the job and set up monitoring per the modelopt-monitor skill. Get the node hostname fromsqueue -j $JOBID -o %N. Bare metal / Docker — use
remote_runto start the server directly:remote_run "nohup python -m vllm.entrypoints.openai.api_server --model <path> --port 8000 > deploy.log 2>&1 &"
- SLURM — see the common skill's
Verify remotely:
remote_run "curl -s http://localhost:8000/health" remote_run "curl -s http://localhost:8000/v1/models"- Report the endpoint — include the remote hostname and port so the user can connect (e.g.,
http://<node_hostname>:8000). For SLURM, note that the port is only reachable from within the cluster network.
For NEL-managed deployment (evaluation with self-deployment), use the evaluation skill instead — NEL handles SLURM container deployment, health checks, and teardown automatically.
Error Handling
| Error | Cause | Fix |
CUDA error: an illegal memory access on an NVFP4 MoE (trtllm_fused_moe_dev_kernel.cu, deepgemm) | Fused-MoE FP4 kernel fault on long-context loads; engine dies, all requests 500 | Try VLLM_USE_FLASHINFER_MOE_FP4=1 + VLLM_FLASHINFER_MOE_BACKEND=throughput. Not always a fix — on DeepSeek-V4 it moved the fault from TRT-LLM to DeepGEMM. It also makes quantized vs baseline not kernel-matched; record that when reporting deltas. |
CUDA out of memory | Model too large for GPU(s) | Increase --tensor-parallel-size or use a smaller model |
quantization="modelopt" not recognized | vLLM/SGLang version too old | Upgrade: vLLM >= 0.10.1, SGLang >= 0.4.10 |
hf_quant_config.json not found | Not a ModelOpt-exported checkpoint | Re-export with export_hf_checkpoint(), or remove --quantization flag |
Connection refused on health check | Server still starting | Wait 30-60s for large models; check logs for errors |
modelopt_fp4 not supported | Framework doesn't support FP4 for this model | Check support matrix in references/support-matrix.md |
Unsupported Models
If the model is not in the validated support matrix (references/support-matrix.md), deployment may fail due to weight key mismatches, missing architecture mappings, or quantized/unquantized layer confusion. Read references/unsupported-models.md for the iterative debug loop: run → read error → diagnose → patch framework source → re-run. For kernel-level issues, escalate to the framework team rather than attempting fixes.
Success Criteria
- Server process is running and healthy (
/healthreturns 200) - Model is listed at
/v1/models - Test generation produces coherent output
- Server URL and port are reported to the user
- If benchmarking was requested, throughput/latency numbers are reported
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

