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 DDS-Solutions/AI-TadPole-OS --skill rust-progit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/rust-pro)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/rust-pro"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/rust-pro/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/dds-solutions/ai-tadpole-os/rust-pro"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/rust-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00039 | $0.00601 |
| Opus 5 | $0.00019 | $0.00300 |
| Sonnet 5 | $0.00008 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
rust-pro 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 8d 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
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / rust-pro
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Rust Systems Engineering & Async Architecture
Philosophy: Zero-cost abstractions. Fearless concurrency. Strict type-level safety. Ecosystem Standard: Rust 1.75+, Tokio runtime, Axum 0.7+,
thiserror,serde.
🎯 Progressive Disclosure & L3 Reference Index
Read REQUIRED core Rust engineering rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/async_axum_and_tokio_patterns.md |
Axum StateHub decomposition, Tokio channel selection, async task spawning | Writing backend routes & Tokio actors |
⚡ 1. Modern Rust Core Principles
- Decomposed State Hubs: In
server-rs, inject state throughAppStatecontaining 5 decoupled hubs (comm,gov,reg,res,sec). - Non-Blocking Runtime: Never call
std::fs,std::thread::sleep, or blocking mutexes in async functions. Usetokio::task::spawn_blockingfor CPU-heavy tasks. - Structured Errors: Use
thiserrorfor domain errors and return explicitResult<T, AppError>. - Zero-Copy Serialization: Leverage
serdewith&str/Cow<'a, str>when deserializing high-throughput JSON.
🛠️ 2. Verification & Lint Gates
# 1. Check syntax and borrow checker
cargo check --manifest-path server-rs/Cargo.toml
# 2. Enforce strict Clippy warnings
cargo clippy --manifest-path server-rs/Cargo.toml -- -D warnings
# 3. Execute unit and integration test suites
cargo test --manifest-path server-rs/Cargo.toml
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.
- 8d ago First seen · 52 lines · 39 tokens per session scan A 5b2ac7fd044a
rust-pro is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 601 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
adapter-express
Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.
trpc-router
Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.
webiny-api-cms-custom-field-type
How to implement a custom CMS field type that integrates with the model builder's fluent API. Covers extending DataFieldBuilder, composing validator interfaces, creating a FieldTypeFactory, registering via DI, and module augmentation for TypeScript autocomplete on the fields() registry.
rust-standards
Rust/Tauri backend standards — L0–L3 layers, centralized platform/net/error ownership, Rust-first business logic, registries, error handling. Load for changes under apps/desktop/src-tauri/src/.
tauri-standards
Tauri shell standards — the IPC 5-step capability flow, command implementation pattern, and capability/permission wiring. Load for new IPC capabilities and changes to commands.rs / tauri-client.ts / capabilities/.