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 Goldziher/ai-rulez --skill pyo3-bindingsgit clone --depth 1 https://github.com/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/pyo3-bindings)<a href="https://agentmods.dev/skills/goldziher/ai-rulez/pyo3-bindings"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/pyo3-bindings/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/goldziher/ai-rulez/pyo3-bindings"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/pyo3-bindings.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.00061 | $0.00322 |
| Opus 5 | $0.00030 | $0.00161 |
| Sonnet 5 | $0.00012 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
pyo3-bindings 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 12d 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
- Use
#[pyclass]and#[pymethods]for Python-visible types. Use#[new]for constructors. - Map Rust
Result<T, E>to Python exceptions viaPyErr. UsePyResult<T>as return type. - Use
pyo3::typesfor conversions. Prefer&stroverStringin parameters, returnString. - Prefer
Bound<'py, T>overPy<T>for ergonomic, lifetime-checked references (PyO3 0.22+). - Release the GIL with
py.allow_threads()for CPU-intensive Rust code. Never hold GIL during I/O. - Use
#[getter]and#[setter]for properties. Implement__repr__and__str__for debugging. - Build with
maturin developfor local testing,maturin build --releasefor distribution. - Test bindings from Python using
pytest. Test both success and error paths. - Keep Python wrappers thin — business logic lives in Rust, Python provides ergonomic API.
- Anti-patterns:
.unwrap()in pyclass methods, blocking GIL for long operations, leaking Python objects.
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.
- 12d ago First seen · 16 lines · 61 tokens per session scan A c767eb99e010
pyo3-bindings is a skill published in the GitHub repository Goldziher/ai-rulez (141 stars, last pushed 4d ago), licensed MIT. It adds 61 tokens to every session and 322 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
pixiv-cli-mcp-tool
Add or change a pixiv-cli MCP tool with full sync of registration, tests, localized MCP docs, README, and CHANGELOG.
test-new-skill
Skill "test-new-skill" from dimetron/pi-go, covering test-new-skill, examples and guidelines.