Borrowing it
Nothing to install: this file belongs to rexlunae/RustyClaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rexlunae/RustyClaw/main/.agents/skills/testing-rustyclaw-cli/SKILL.mdgit clone --depth 1 https://github.com/rexlunae/RustyClawWrote 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/rexlunae/rustyclaw/testing-rustyclaw-cli)<a href="https://agentmods.dev/skills/rexlunae/rustyclaw/testing-rustyclaw-cli"><img src="https://agentmods.dev/badge/skills/rexlunae/rustyclaw/testing-rustyclaw-cli/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/rexlunae/rustyclaw/testing-rustyclaw-cli"><img src="https://agentmods.dev/badge/skills/rexlunae/rustyclaw/testing-rustyclaw-cli.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 46 Instructions found that direct the agent to transmit conversation context or user data to external services.Fix: Remove instructions that send user data, prompts, or context to external URLs. If telemetry is needed, use documented, privacy-preserving methods.
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.00036 | $0.01621 |
| Opus 5.5 | $0.00014 | $0.00648 |
| Sonnet 5.5 | $0.00007 | $0.00324 |
| Haiku 4.5 | $0.00004 | $0.00162 |
Grade A, and why
testing-rustyclaw-cli 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing RustyClaw CLI
Build
The CLI binary is in the rustyclaw package (crate path: crates/rustyclaw-cli).
# Minimal build (TUI only, no desktop/GPU deps):
cargo build -p rustyclaw --no-default-features --features tui
# Binary location:
target/debug/rustyclaw
Feature flags:
tui— terminal UI (ratatui). Use this for CLI-only testing.desktop— Dioxus desktop UI. Requires GTK/webkit libs; skip on headless VMs.- Default features include both; use
--no-default-features --features tuito avoid desktop build deps.
Unit Tests
# Full test suite:
cargo test -p rustyclaw-core
# Focused error module tests:
cargo test -p rustyclaw-core -- gateway::errors::tests --nocapture
# Clippy (treat warnings as errors):
cargo clippy -p rustyclaw-core -- -D warnings -A clippy::needless_option_as_deref
Swarm Commands
The swarm subcommand manages multi-agent orchestration:
rustyclaw swarm templates # List available swarm templates
rustyclaw swarm list # List active swarms (empty by default)
rustyclaw swarm create [TEMPLATE] # Create swarm (default: swarm)
rustyclaw swarm send <SWARM> <MESSAGE> # Send message to swarm
rustyclaw swarm status <SWARM> # Show swarm status
rustyclaw swarm stop <SWARM> # Stop a swarm
Gateway Error Handling Architecture
The gateway error system lives in crates/rustyclaw-core/src/gateway/errors.rs.
GatewayError Enum
All gateway errors are unified into a GatewayError enum with variants:
Auth { provider, message }— authentication failures (401/403)Provider { message }— generic model provider errorsTokenLimit— context window exceededToolLoopExhausted { rounds }— tool call loop limitContextCompaction { message }— non-fatal compaction failureCancelled— user cancellationVault { message }— vault/secret storage errorsDeviceFlow { message }— OAuth device flow failuresConfig { message }— configuration errorsTokenRefresh { message }— OAuth token refresh failuresUnexpectedFinish { reason }— model finished with unusual finish_reason
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.
- 2mo ago First seen · 148 lines · 36 tokens per session scan A bd34e9b6aa24
testing-rustyclaw-cli is a skill published in the GitHub repository rexlunae/RustyClaw (61 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,621 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
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.