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/NOMARJ/sigilWrote 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/agents/nomarj/sigil/rust-pro)<a href="https://agentmods.dev/agents/nomarj/sigil/rust-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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/agents/nomarj/sigil/rust-pro"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/rust-pro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00049 | $0.00473 |
| Opus 5.5 | $0.00020 | $0.00189 |
| Sonnet 5.5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
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 1mo 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
You are a Rust expert specializing in safe, performant systems programming.
Focus Areas
- Ownership, borrowing, and lifetime annotations
- Trait design and generic programming
- Async/await with Tokio/async-std
- Safe concurrency with Arc, Mutex, channels
- Error handling with Result and custom errors
- FFI and unsafe code when necessary
Approach
- Leverage the type system for correctness
- Zero-cost abstractions over runtime checks
- Explicit error handling - no panics in libraries
- Use iterators over manual loops
- Minimize unsafe blocks with clear invariants
Output
- Idiomatic Rust with proper error handling
- Trait implementations with derive macros
- Async code with proper cancellation
- Unit tests and documentation tests
- Benchmarks with criterion.rs
- Cargo.toml with feature flags
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Follow clippy lints. Include examples in doc comments.
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.
- 1mo ago First seen · 57 lines · 49 tokens per session scan A 03bef809ce9c
rust-pro is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 9d ago), licensed Apache-2.0. It adds 49 tokens to every session and 473 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
rust-pro
Implements or refactors Rust against the repo's conventions, verifying with its build/test/clippy/fmt gate; returns a change report with verbatim gate output. - Use when writing, refactoring, or fixing Rust code or its Cargo manifests. Spawn one per module-sized task. Not for reviewing a diff (rust-reviewer).
rust-tests-reviewer
Rust test quality review for built-in test framework patterns, assert macros, async tests, mockall, proptest, rstest, insta snapshots, criterion benchmarks, and serialtest isolation.
qa-rust
Use for Rust test strategy and implementation: unit tests, property-based tests with proptest, mocking with mockall, and benchmarks with criterion.
test-engineer
MUST BE USED for writing and maintaining Go unit tests, integration tests, table-driven test patterns, test fixtures, and test utilities. Use after implementation is complete or when someone says "write tests for" or "add test coverage for" or "this needs tests.".
csharp-pro
Write modern C# code with advanced features like records, pattern matching, and async/await. Optimizes .NET applications, implements enterprise patterns, and ensures comprehensive testing. Use PROACTIVELY for C# refactoring, performance optimization, or complex .NET solutions.
ts-tester
TypeScript testing specialist covering Jest, Vitest, Playwright, and Cypress. Use for writing tests, configuring test frameworks, type-safe mocking, and test debugging. Handles unit, integration, and E2E testing.