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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/plugins/nodnarbnitram/claude-code-extensions/cce-tauri)<a href="https://agentmods.dev/plugins/nodnarbnitram/claude-code-extensions/cce-tauri"><img src="https://agentmods.dev/badge/plugins/nodnarbnitram/claude-code-extensions/cce-tauri.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cce-tauri 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 3d 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
83% identical to cce-anthropic — 15 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.
What it actually says
{
"name": "cce-tauri",
"version": "1.0.1",
"description": "Tauri v2 desktop and mobile app development with Rust backend, IPC, capabilities, and security",
"author": {
"name": "Claude Code Extensions Contributors",
"url": "https://github.com/nodnarbnitram/claude-code-extensions"
},
"homepage": "https://github.com/nodnarbnitram/claude-code-extensions",
"repository": "https://github.com/nodnarbnitram/claude-code-extensions",
"license": "MIT",
"keywords": [
"tauri",
"desktop",
"rust",
"ipc",
"capabilities"
]
}
What it installs
The manifest is a name and a version. 1 agent travel with it, and installing the plugin installs all of them — 79 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 20 lines scan A 30d1139cfa51
cce-tauri is a plugin published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. It is 83% identical to cce-anthropic, differing in 15 lines, and is treated as a copy.
Other plugins, from other repositories
tauri-development
Tauri 2 desktop and mobile development - IPC optimization, Rust backend patterns, cross-platform builds, and React integration for high-performance apps.
rust-tools
SOTA Rust tooling - refactoring, profiling, benchmarking, testing, SIMD, dependency audit.
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
mwdat-ios
Git-native DAT SDK guidance for ios development, covering setup, camera streaming, display access, MockDeviceKit, session lifecycle, permissions, debugging, and sample app patterns.
dd:rust
Rust conventions and best practices for Claude Code.
swift
Swift programming language utilities and migration tools for Claude Code.