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 randommonicle/claude-skills --skill one-real-ridegit clone --depth 1 https://github.com/randommonicle/claude-skillsWrote 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/randommonicle/claude-skills/one-real-ride)<a href="https://agentmods.dev/skills/randommonicle/claude-skills/one-real-ride"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/one-real-ride/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/randommonicle/claude-skills/one-real-ride"><img src="https://agentmods.dev/badge/skills/randommonicle/claude-skills/one-real-ride.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.00137 | $0.00772 |
| Opus 5 | $0.00068 | $0.00386 |
| Sonnet 5 | $0.00027 | $0.00154 |
| Haiku 4.5 | $0.00014 | $0.00077 |
Grade A, and why
one-real-ride 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
One real ride
Seven incidents where every automated gate was green and the feature was broken in production or the UI, plus a schema change that broke every report for five days while tsc and the whole test suite stayed green. The pattern is always the same: each layer was proven alone, and the defect lived in a seam between them. Layer: the done-gate hub.
The rule
Before "done": one real end-to-end invocation of the changed path, through the real seams — the deployed function (not the local one), a real authenticated session (not a service-role shortcut), the real model call, the real browser or the real device. The smoke proves the layer; the ride proves the seams.
What counts as a seam
- Deployed runtime vs local: a deployed Edge Function 500'd on a dropped column CI could not see.
- Auth: a function's own role pre-check was wrong in a way its smoke structurally could not catch.
- Type-check vs render: "tsc green is not a working UI" — twice, including a Rules-of-Hooks blank page.
- Build vs dev server: they run different code paths; a green production build does not prove the dev server boots, and vice versa.
- Merge vs ship: know the deploy path per change type — a server merge may be live in minutes while an app merge reaches nobody until the next signed build. A merge is never a device test; the device test is the gate for device- or WebView-specific code.
- Inherited guards and configs: anything borrowed from a sibling surface was calibrated for its original inputs — the first real invocation is what catches the mis-calibration three reviews missed.
- Schema: after any migration existing code reads, ride the highest-value path once (generate the report, make the request). It is the only check that catches what synthetic-data tests cannot.
Routes
- Interpreting any individual success signal during the ride → verify-the-effect (the norm; its playbook holds the diagnostics discipline).
- The change sends transactional email → email-delivery-verification.
- The change involved env vars, CI secrets, or hosted config → env-change-verification.
- The change touched build config, lockfiles, or toolchain → reproduce-the-real-build.
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 · 48 lines · 137 tokens per session scan A e66ad70d5fc8
one-real-ride is a skill published in the GitHub repository randommonicle/claude-skills (23 stars, last pushed 6d ago), licensed Apache-2.0. It adds 137 tokens to every session and 772 once invoked, about $0.0007 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-31.
Other skills, from other repositories
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.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…