Borrowing it
Nothing to install: this file belongs to remyxai/outrider. 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/remyxai/outrider/main/.claude/skills/outrider-experimentation/SKILL.mdgit clone --depth 1 https://github.com/remyxai/outriderWrote 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/remyxai/outrider/outrider-experimentation)<a href="https://agentmods.dev/skills/remyxai/outrider/outrider-experimentation"><img src="https://agentmods.dev/badge/skills/remyxai/outrider/outrider-experimentation/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/remyxai/outrider/outrider-experimentation"><img src="https://agentmods.dev/badge/skills/remyxai/outrider/outrider-experimentation.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.00130 | $0.02547 |
| Opus 5.5 | $0.00052 | $0.01019 |
| Sonnet 5.5 | $0.00026 | $0.00509 |
| Haiku 4.5 | $0.00013 | $0.00255 |
Grade A, and why
outrider-experimentation 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Outrider experimentation — field guide
Ambient knowledge for using Outrider effectively on target repos: from dispatch to upstream. All commands here are ones I've actually used in practice; nothing speculative.
When to use
- Setting up Outrider on a new target repo
- Dispatching a manual refinement / smoke run
- Diagnosing why a run downgraded to Issue or opened at a different outcome than expected
- Deciding whether an Outrider-drafted PR is ready to file upstream
- Cross-checking a paper against existing coordination signals on the target repo
Set up Outrider on a target repo
Fastest path — CLI-generated workflow with the right backend selected:
remyxai outrider setup-local --repo owner/name --backend moonshot
Backends: anthropic (default, Opus), zai (GLM), moonshot (Kimi K3). Setup-local prompts only for the selected backend's secret; add others manually via gh secret set ANTHROPIC_API_KEY --repo owner/name < token.txt for per-dispatch switching.
Manual install (when the CLI shape doesn't quite fit): copy the workflow YAML from remyxai/outrider's .github/workflows/outrider.yml and thread the interest-id you get from remyxai interests get -f json.
Trigger manually
# Fresh recommend (let selection pass pick)
gh workflow run outrider.yml --repo owner/name --ref main
# Pin to a specific paper (skip selection)
gh workflow run outrider.yml --repo owner/name --ref main \
-f pin-arxiv=2509.09675v1 \
-f provider=moonshot \
-f model=kimi-k3
# Refinement on an existing drafter branch
gh workflow run outrider.yml --repo owner/name --ref main \
-f pin-arxiv=<id> \
-f start-from-ref=<drafter-branch> \
-f staged-synthesis=true \
-f lead-content="REFINEMENT PASS on existing branch..."
# Convention pass on an already-open PR
gh workflow run outrider-convention.yml --repo owner/name --ref main -f pr-number=18
Key inputs to remember:
pin-arxiv: exact<id>[v<N>]— bypasses selection, best for reproducible runspin-method: free-text query for the selection pass to search (often prefersearch-method;pin-methodis a docs-only alias that GHA warns about)start-from-ref: refinement mode — pins to an existing branchstaged-synthesis=true: enables research phase before coding (adds ~10 min for slow backends)claude-timeout: bump to3600for Kimi K3 or GLM-5.2 (thinking-mode adds per-turn latency)rate-limit-days=0: bypass the 7-day cadence guard for one-off smokes
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 · 182 lines · 130 tokens per session scan A 2d60bbfb8329
outrider-experimentation is a skill published in the GitHub repository remyxai/outrider (26 stars, last pushed 2d ago), licensed Apache-2.0. It adds 130 tokens to every session and 2,547 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
arxiv-mcp-server
Use when finding, comparing, reading, or monitoring arXiv papers, including requests for abstracts, citation graphs, original LaTeX, section-level technical details, or literature reviews.
iso-24495-3
Sector-specific Plain Language standard for science and technical writing (ISO 24495-3:2026). Applied during software documentation, architecture specs, and technical analysis.
emem-field-tokens
Fetches a native-resolution raster field over an area from emem, or the same field over several dates, as a signed and re-derivable artifact rather than a set of per-cell scalars. Use when the user needs the actual grid of values over an area of interest (a world-model input, a band or NDVI drape, change analysis over…
emem-eudr-due-diligence
Produces a signed, Annex II shaped Due Diligence Statement under the EU Deforestation Regulation (EU 2023/1115) for one or more production plots with emem, and explains what it proves and what it leaves to the operator. Checks each plot against the JRC GFC2020 forest baseline and Hansen Global Forest Change loss year…
emem-locate-and-recall
Resolves a place name to an emem cell64 address and recalls signed Earth-observation facts there (weather, vegetation indices, elevation, soil, land cover, surface water, forest change). Use when the user asks for a measurable value at a named place ("what is the temperature in Bengaluru", "how high is Denali", "what…
emem-document-evidence
Turns a scanned document into signed, checkable evidence with emem. Runs OCR on an image, then parses a pesticide-residue lab report (analytes, results in mg/kg, LOQ, printed MRL, exceedances) or a land record (owners, parcel ids, areas in hectares, places, dates), with every value tied to its line and byte offset and…