Rust toolchain and debuggers, optimized for Rust development, token efficiency, with agents to task
2.4K
Cost savings: use the tweakcc reduced system prompt + specialized Rust tools for the best results. A default Claude Code prompt injects 30K+ characters per turn — that's $90/MTurn on Sonnet and $150 on Opus for tokens you never read. The tweakcc thinkingVerbs and ablated prompts trim this to ~10K, saving up to 90% on cached reads and ~$4.50/hour in input for a coding session at 100 requests/hour.
Drop a Rust project into a container and ask Claude to compile, lint, cross-compile, and ship it. This image combines Claude Code (abliterated) with Rust, clippy, rust-analyzer, and cargo subcommands — a complete Rust development workstation with cross-compilation support.
This container is a focused Rust development environment. Mount whatever Rust crates, libraries, or CLI tools you want to work on, start the container, and Claude automatically gets:
No configuration, no setup. Give it a Rust crate and ask Claude to build, lint, cross-compile, and ship.
# First, navigate to your project directory.
# cd $HOME/git/my-project
# Build a Rust project with Claude and clippy working together
docker run -u $(id -u):$(id -g) -e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest
# Or with podman:
podman run -u $(id -u):$(id -g) --userns=keep-id \
-e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest
# Then send a prompt:
# "clippy my project, run cargo audit, and cross-compile to aarch64"
# Or with a local Ollama model:
docker run -u $(id -u):$(id -g) -e OLLAMA_MODEL=gemma4:31b \
-e OLLAMA_HOST=10.12.2.4 \
-e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest
# Or with podman:
podman run -u $(id -u):$(id -g) --userns=keep-id \
-e OLLAMA_MODEL=gemma4:31b \
-e OLLAMA_HOST=10.12.2.4 \
-e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest
Claude connects to the rust-analyzer server, calls cargo clippy, traces dependencies via cargo-deny, and returns a natural-language report — all from one prompt.
Building Rust applications typically means installing the Rust toolchain, setting up CARGO_HOME/RUSTUP_HOME, and installing multiple cargo subcommands. This container bundles it all and makes it accessible to Claude via a single -p prompt.
| Without this container | With rust-claude-abliterated |
|---|---|
| Install Rust, clippy, rust-analyzer, cargo subcommands | docker run — everything is ready |
| Write Rust code, run clippy, cargo-audit, cargo-deny manually | Claude calls cargo clippy and gets actionable fixes directly |
| Manually manage Cargo.toml, Cargo.lock, cross-compilation targets | Ask Claude — it knows the Cargo ecosystem |
| Cross-compile with sysroots and toolchain setup | Built-in cross-compilation targets (gnu + musl) |
| Manual cargo.toml and clippy.toml configuration | Pre-configured clippy.toml and cargo_deny.toml |
The container works with any Rust project under /workdir:
| Component | Source | Description |
|---|---|---|
| Rust | rustup.rs | Core toolchain (rustc, cargo, rustfmt, rustdoc) |
| Claude Code | claude-abliterated/ | Abliterated CLI with tweakcc, 200+ skills, rules |
| clippy | rustup component | 800+ lints (correctness, style, complexity, perf) |
| rust-analyzer | rustup component | Language Server Protocol server |
| cargo-expand | crates.io | Macro expansion and code inspection |
| cargo-audit | crates.io | Security scanning (RustSec advisory database) |
| cargo-edit | crates.io | Cargo.toml management (add, remove, set, upgrade) |
| cargo-outdated | crates.io | Dependency version checking |
| cargo-semver-checks | crates.io | API semver compliance |
| cargo-tarpaulin | crates.io | Code coverage (HTML, JSON, XML) |
| cargo-deny | crates.io | License + advisory + dependency checks |
| cargo-make | crates.io | Build automation (Cargo.toml-based Makefile) |
Prompt Claude to use clippy linting practices. You can say "use the rust skill to check my crate, fix clippy warnings, and ensure functions are not too complex" and Claude will apply Rust-specific linting rules, break tasks down properly, and mock test each segment for efficacy.
Directed skills improve code quality and resilience. With abliterated Claude and directed skills:
Say "use the rust skill to..." to directly task Claude with Rust-specific skills — clippy linting, cargo build/test, macro expansion with cargo-expand, and security scanning with cargo-deny.
Extends Claude Code with specialized command-line tools. Available scripts are automatically in $PATH and activate via slash commands or Claude's built-in tool use:
claude-fix # Fix code issues with context-aware edits
claude-ask # Ask questions, get answers without side effects
claude-bash # Run bash with smarter timeouts and session persistence
claude-agent # Launch Claude as a persistent agent
To invoke the claude-tools development shell, add /bin/bash to your docker run or podman run command. This starts an interactive shell where claude-tools are available on $PATH and Claude Code is configured for development:
# claude-tools development shell with Docker
docker run -u $(id -u):$(id -g) -e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest /bin/bash
# Or with podman:
podman run -u $(id -u):$(id -g) --userns=keep-id \
-e ANTHROPIC_API_KEY=sk-... \
-v "$PWD:/workdir:rw" \
t2fn/rust-claude-abliterated:latest /bin/bash
From the shell you can run claude-fix, claude-ask, claude-bash, claude-agent, and send slash commands (/fix, /ask, /plan) directly to Claude. Use claude-fix --comment to post inline PR comments or --fix to apply findings directly.
More examples: mijuny/claude-tools/tree/main/README.md
This container runs on claude-abliterated:rocky10, which uses the tweakcc (tweakcc-fixed) reduced system prompt to cut ~67% off daily-flow prompts — from ~30K to ~10K characters. For Rust development, this means:
"Claude" and "Claude Code" are registered trademarks of Anthropic, PBC. This project uses the name "Claude" in a nominative (descriptive) sense — it identifies the Anthropic product (Claude Code) that this project is built to work with, consistent with the nominative fair use doctrine. The use is necessary: a third-party project cannot refer to "Claude Code" without using the mark itself.
This project is not affiliated with, endorsed by, or sponsored by Anthropic, PBC. The name "rust-claude-abliterated" is a third-party project name where:
The project uses both "Rust" and "Claude" to describe what it works with, not who it is from.
All other trademarks belong to their respective owners. No implication of endorsement is made by the use of these marks.
| Container | Purpose | Hub |
|---|---|---|
| asm-claude-abliterated | Cross-architecture assembly dev stack | Hub |
| gcc-claude-abliterated | C/C++ development with GCC + valgrind | Hub |
| golang-claude-abliterated | Go development with gopls + golangci-lint | Hub |
| python-claude-abliterated | Python linting with ruff + mypy | Hub |
| rust-claude-abliterated | Rust dev with clippy + cargo | Hub |
| java-claude-abliterated | Java/Spring Boot with Maven + Gradle | Hub |
| typescript-claude-abliterated | TypeScript dev with biome + eslint | Hub |
| hdl-claude-abliterated | FPGA/ASIC HDL dev (iverilog, ghdl, verilator) | Hub |
| ada-claude-abliterated | Ada development (GNAT via alr, AUnit testing) | Hub |
| cobol-claude-abliterated | COBOL compilation for mainframe modernization | Hub |
| julia-claude-abliterated | Julia scientific computing and IJulia notebooks | Hub |
| apache-claude-abliterated | Apache Spark + Pig big data processing | Hub |
| fortran-claude-abliterated | Fortran HPC with BLAS/LAPACK math libs | Hub |
| ghidra-claude-abliterated | Ghidra reverse engineering and malware inspection | Hub |
Source code and suggestions/issues/pull requests can be made at:
Content type
Image
Digest
sha256:73a20463d…
Size
2 GB
Last updated
about 1 month ago
docker pull t2fn/rust-claude-abliterated