Borrowing it
Nothing to install: this file belongs to r3bl-org/r3bl-open-core. 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/r3bl-org/r3bl-open-core/main/.agents/skills/test-cross-platform/SKILL.mdgit clone --depth 1 https://github.com/r3bl-org/r3bl-open-coreWrote 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/r3bl-org/r3bl-open-core/test-cross-platform)<a href="https://agentmods.dev/skills/r3bl-org/r3bl-open-core/test-cross-platform"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/test-cross-platform/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/r3bl-org/r3bl-open-core/test-cross-platform"><img src="https://agentmods.dev/badge/skills/r3bl-org/r3bl-open-core/test-cross-platform.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.00031 | $0.01640 |
| Opus 5.5 | $0.00012 | $0.00656 |
| Sonnet 5.5 | $0.00006 | $0.00328 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
test-cross-platform 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 11d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Platform Fleet Testing
Run the full test suite across the remote cross-platform fleet (Linux on nazmul-mobile.local, macOS, and Windows)
to verify compatibility, platform gates, and asynchronous I/O behavior.
When to Use
- After modifying cross-platform code, platform-specific
#[cfg(...)]gates, or PTY logic. - Before merging pull requests or finalizing release milestones.
- When the user runs
/test-cross-platformor asks to test across platforms/fleet.
Worktree & Folder Detection
The skill dynamically detects whether you are in the primary repository or a git worktree:
# Fish syntax:
set -l REPO_ROOT (git rev-parse --show-toplevel)
set -l FOLDER_NAME (basename "$REPO_ROOT")
# Bash syntax:
REPO_ROOT=$(git rev-parse --show-toplevel)
FOLDER_NAME=$(basename "$REPO_ROOT")
If you are in ~/github/roc, $FOLDER_NAME is roc. If you are in a worktree such as ~/github/roc-fix-shift-home-lockup, $FOLDER_NAME is roc-fix-shift-home-lockup. Remote fleet machines mirror this folder under their respective repository parent paths.
Worktree Portability & Relative Paths (worktree.useRelativePaths)
Linked git worktrees store administrative pointer files:
- Inside the worktree:
.git(file containinggitdir: <path_to_main_repo>/.git/worktrees/<name>) - Inside the main repo:
.git/worktrees/<name>/gitdir(file containing<path_to_worktree>/.git)
By default, Git writes absolute paths (/home/nazmul/... on Linux vs /Users/nazmul/... on macOS). If worktrees or their .git files are mirrored across systems with different home directory roots, Git will fail on the remote host with:
fatal: not a git repository: (null)
which causes any tests or tools that invoke git (such as cargo-rustdoc-fmt validation tests in build-infra) to fail.
To prevent this:
- Always enable relative worktree paths globally:
Or explicitly passgit config --global worktree.useRelativePaths true--relativewhen creating a worktree:git worktree add --relative ../<worktree_folder> <branch> - To repair existing worktrees with absolute path mismatches:
Git will detect the absolute path mismatch and convert all linked worktrees to relative paths in place.cd ~/github/roc git config worktree.useRelativePaths true git worktree repair
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.
- 11d ago Changed db0059429db8
- 15d ago Changed · +53 lines · +2 tokens per session 916662dacc5c
- 1mo ago First seen · 89 lines · 29 tokens per session scan A d0d2708a79fb
test-cross-platform is a skill published in the GitHub repository r3bl-org/r3bl-open-core (486 stars, last pushed yesterday), licensed Apache-2.0. It adds 31 tokens to every session and 1,640 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-09.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
cw-dogfood
Use when a Codewhale change needs proving in the real product, or when asked to build/install/dogfood the local binaries: stamped release build, atomic install, fresh-shell verification, and the manual QA that gates cannot cover.
gmail
Search, read, draft, and send Gmail when the user asks to work with their inbox or email.
google-calendar
Read schedules, check availability, and create or update Google Calendar events when the user asks to work with their calendar.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.