options-backtest SKILL.md skillA
options-backtest from iman/agent-driven-options-desk-and-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add iman/agent-driven-options-desk-and-skills/options-backtest@git:20260910.36bb573Pins git:20260910.36bb573 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- iman/agent-driven-options-desk-and-skills
- Path
shell/skills/options-backtest/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260910.36bb573, committed Sep 10, 2026
- First version recorded
- Aug 31, 2026
- Size
- 6,832 bytes
- Repository stars
- 11
- License
- a license file GitHub does not identify
Test an option structure against real price history with modelled premiums, and run a paper forward test that records positions before their outcome is known and marks them against later chains. Reports win rate, mean return on capital at risk, drawdown, a permutation test, a bootstrap interval and a buy-and-hold benchmark. Use when the user asks whether a strategy has worked historically, to backtest or forward test something, whether an edge is real or chance, how a structure performed, or…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Backtest and forward test Two different questions. A backtest asks what a rule would have done. A forward test asks what a position actually did from the moment it was written down. ## Execution route Prefer the `option_backtest` MCP tool for a backtest and the `option_forward_test` MCP tool for the paper ledger. If the matching tool is not available, use the `optiondesk` commands below. If neither MCP nor the CLI is available, say that no fresh result can be produced; do not invent figures or present an example or remembered result as a new analysis. ## Data boundary Use fresh provider data only when the tool reports that access is allowed. A local Yahoo adapter also requires the personal-use acknowledgement. A hosted tool must use a provider that is approved for public display, derived outputs, storage, and MCP delivery. Never bypass a provider refusal. When no approved tool is available, analyse a snapshot that the user supplied and had the right to share. Otherwise, state that current figures are unavailable. ## Backtest ``` optiondesk backtest SPY iron_condor --holding-days 30 --entry-every 5 --period 5y ``` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_hgvzezn4eg6oz4c4/0813ee912c75071a63027f9472baf274141d63c3cc27ab788d91780bb7330b0c.json
Then /plugin install options-backtest@markdownregistry-hgvzezn4eg6oz4c4 in Claude Code. It installs git:20260910.36bb573, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add iman/agent-driven-options-desk-and-skills/options-backtest@sha256:0813ee912c75071aThe line at the top of this page pins the label git:20260910.36bb573, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hgvzezn4eg6oz4c4)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in iman/agent-driven-options-desk-and-skills/options-backtest since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of options-backtest from somewhere else? Ask it: where did my options-backtest come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Aug 31, 2026 and Sep 10, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260910.36bb573 latest | 2026-09-10 | 36bb573 | 6,832 B | A | view · diff |
| git:20260902.060fb4c | 2026-09-02 | 060fb4c | 6,540 B | A | view · diff |
| git:20260831.ed610db | 2026-08-31 | ed610db | 6,067 B | A | view · diff |
| git:20260831.9cf03b1 | 2026-08-31 | 9cf03b1 | 4,673 B | A | view · diff |
| git:20260831.06e0205 | 2026-08-31 | 06e0205 | 4,049 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/options-backtest/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6832 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
iman/agent-driven-options-desk-and-skills · 11 stars · license a license file GitHub does not identify · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hgvzezn4eg6oz4c4 GET https://markdownregistry.com/api/v1/resolve?ref=iman/agent-driven-options-desk-and-skills/options-backtest GET https://markdownregistry.com/api/v1/blob/0813ee912c75071a63027f9472baf274141d63c3cc27ab788d91780bb7330b0c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from iman/agent-driven-options-desk-and-skills
Every file in iman/agent-driven-options-desk-and-skills