RPent is an open framework for building embodied agents, software systems that perceive and act in the physical world while combining reasoning, memory, execution, and adaptation. It is intended for embodied-intelligence researchers working on physical tasks and related evaluations.
Borrowing it
Nothing to install: this file belongs to RLinf/RPent. 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/RLinf/RPent/main/.agents/skills/verify-change/SKILL.mdgit clone --depth 1 https://github.com/RLinf/RPentWrote 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/rlinf/rpent/verify-change)<a href="https://agentmods.dev/skills/rlinf/rpent/verify-change"><img src="https://agentmods.dev/badge/skills/rlinf/rpent/verify-change/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/rlinf/rpent/verify-change"><img src="https://agentmods.dev/badge/skills/rlinf/rpent/verify-change.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.00035 | $0.00629 |
| Opus 5.5 | $0.00014 | $0.00252 |
| Sonnet 5.5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
verify-change 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify a change
Read CONTRIBUTING.md, tests/README.md, and the affected CI workflow. Use their current commands and prerequisites; reuse existing runners and fixtures.
Select checks
- Identify changed behavior and its callers before selecting tests. Use focused cases during development, then the required repository checks before a PR.
- Core Python changes use
tests/unit_tests/rpent/; robot adapters usetests/unit_tests/robots/. Unit tests run offline on CPU. Add or extend tests for observable new behavior or a concrete regression, rather than mirroring implementation details or creating a parallel test framework. - Documentation changes use docs-check. Dependency, optional-import, CLI, or robot-discovery changes also need the relevant installation and startup checks in the affected environment.
- Env/VLA or runtime changes may need the real component and policy-chain tests documented in the test guide. Check GPU, assets, checkpoint, and platform prerequisites before launching them.
Run existing commands
Use an isolated environment as described in CONTRIBUTING. Before opening a PR, run from the repository root:
pre-commit run --all-files
pytest tests/unit_tests -v
Inspect any files changed by hooks and rerun affected checks. The unit-test workflow defines the full Python matrix and additional Flywheel dependencies; one local environment does not cover that matrix. Do not install every robot extra for an unrelated change.
For the supported GPU suites, follow the environment setup in the test guide and call the existing runner:
bash tests/e2e_tests/run_gpu_suite.sh \
<libero-pro|robocasa|robotwin> \
/path/to/new-output-dir \
/path/to/new-venv-root
Choose the actual target and fresh paths. Inspect the runner's logs, JUnit results, and cleanup evidence. Real-robot diagnostics are separate opt-in procedures with operator prerequisites; follow their documented scope rather than treating them as ordinary automated checks.
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 · 68 lines · 35 tokens per session scan A 89e26a56fea6
verify-change is a skill published in the GitHub repository RLinf/RPent (1,640 stars, last pushed 3d ago), licensed Apache-2.0. It adds 35 tokens to every session and 629 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-09-17.
Other skills, from other repositories
agent-tester
Agent skill for tester - invoke with $agent-tester.
web3-testing
Test smart contracts comprehensively using Hardhat and Foundry with unit tests, integration tests, and mainnet forking. Use when testing Solidity contracts, setting up blockchain test suites, or validating DeFi protocols.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
python-testing
Guidelines for writing and running tests in the Agent Framework Python codebase. Use this when creating, modifying, or running tests.
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
dbt-transformation-patterns
Master dbt (data build tool) for analytics engineering with model organization, testing, documentation, and incremental strategies. Use when building data transformations, creating data models, or implementing analytics engineering best practices.