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 agentmods add skills/the-open-engine/zeroshot/opcorenpx skills add the-open-engine/zeroshot --skill opcoregit clone --depth 1 https://github.com/the-open-engine/zeroshotWrote 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/the-open-engine/zeroshot/opcore)<a href="https://agentmods.dev/skills/the-open-engine/zeroshot/opcore"><img src="https://agentmods.dev/badge/skills/the-open-engine/zeroshot/opcore.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00306 |
| Opus 5 | $0.00009 | $0.00153 |
| Sonnet 5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
opcore 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 3d 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.
What it actually says
Opcore
Opcore is Zeroshot's packaged, repository-local constraints gate. It supplements rather than replaces the repository's lint, type, test, CI, and review guardrails.
- Run
npm run opcore:statusbefore broad work. If the persistent graph is stale, runnpm run opcore:graph:build; after source changes, refresh it withnpm run opcore:graph:update. - Use
opcore graph search,impact, andreview-context, plusopcore inspect definition,references,signature, andimplementations, when graph-backed evidence will reduce uncertainty. - Use
opcore validate hypotheticalor the installed pre-write hook before a proposed write when the harness does not invoke the hook automatically. - Run
npm run opcore:checkbefore finalizing source edits. This gate reports only diagnostics introduced relative to the Git base; existing repository debt is not a blocking result. - Run
npm run opcore:scanandnpm run opcore:measurefor named repository metrics and deltas, not as opaque ratings. - Treat unsupported stacks, unavailable tools, stale graphs, and indeterminate results honestly; never report them as clean coverage.
- Preserve all existing repository guardrails. A full-tree
opcore check allis an audit command, not a blocking commit, CI, or agent gate.
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.
- 3d ago First seen · 17 lines · 17 tokens per session scan A 01055bcf1aaa
opcore is a skill published in the GitHub repository the-open-engine/zeroshot (1,815 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 306 once invoked, about $0.0001 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-30.
Other skills, from other repositories
analyze-performance-traces
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…
tutti-test-audit
Audit, design, write, materially revise, or remove Tutti tests. Use whenever Codex changes or reviews unit, component, conformance, integration, regression, platform, or repository tests; enforce a protected product contract, credible failure, correct owning boundary, negative-control evidence, overlap review…
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
babysit
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.).
parallel-orchestration
Coordinate multiple specialized agents across parallel work streams with quality gates and conflict resolution.