Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add asfbay-bit/opchain-skills/plugin install opchainWrote 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/asfbay-bit/opchain-skills/oc-reverse-spec)<a href="https://agentmods.dev/skills/asfbay-bit/opchain-skills/oc-reverse-spec"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-reverse-spec/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/asfbay-bit/opchain-skills/oc-reverse-spec"><img src="https://agentmods.dev/badge/skills/asfbay-bit/opchain-skills/oc-reverse-spec.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.00055 | $0.06046 |
| Opus 5 | $0.00028 | $0.03023 |
| Sonnet 5 | $0.00011 | $0.01209 |
| Haiku 4.5 | $0.00006 | $0.00605 |
Grade A, and why
oc-reverse-spec 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 5d 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 — 603 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reverse Spec
On first invocation, read references/orchestrator.md and follow its welcome protocol.
Read an existing codebase and generate the structured spec documents that oc-app-architect expects as inputs. This is the reverse of the normal pipeline: instead of idea → spec → code, it goes code → spec → pipeline-ready.
Why This Exists
The build pipeline (oc-app-architect Phase 2 stack decision → Phase 6 build loop) assumes spec documents exist. But most real projects were built before the pipeline existed, or grew organically without formal specs. Reverse-spec bridges that gap — it reads what's actually built and produces the documentation that makes the project legible to the rest of the toolchain.
This matters because without specs:
- oc-app-architect can't generate a roadmap for new features (no baseline to build from)
- oc-stack-forge can't run a gap analysis (no documented architecture to compare against)
- oc-app-architect Phase 6 can't decompose features into sprints (no spec.md or sprint-plan.md to reference)
/oc-reverse-spec — Command Reference
When the user types /oc-reverse-spec, display this menu:
REVERSE SPEC COMMANDS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
MODES
/oc-rev-scan Quick scan — inventory what exists, recommend spec priority
/oc-rev-full Full spec generation — produce all oc-app-architect spec docs
/oc-rev-design Design system extraction — colors, typography, components
/oc-rev-stack Stack-forge gap analysis — typed pipeline audit
/oc-rev-sprint Tri-dev onramp — generate spec.md + sprint-plan.md for a feature
UTILITIES
/oc-rev-status Show progress from checkpoint — what's done, what's next
/oc-rev-diff Compare generated specs against actual code (drift check)
SESSION
/checkpoint Show checkpoint status
/checkpoint show Display full checkpoint JSON
/checkpoint reset Archive and clear checkpoint
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Type any command to begin. /oc-reverse-spec to see this again.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed d66c0f0a7869
- 9d ago First seen · 603 lines · 55 tokens per session scan A 2cfade31580a
oc-reverse-spec is a skill published in the GitHub repository asfbay-bit/opchain-skills (0 stars, last pushed 4d ago), licensed Apache-2.0. It adds 55 tokens to every session and 6,046 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…