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 Jamie-BitFlight/claude_skills/plugin install dhWrote 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/jamie-bitflight/claude_skills/interop)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/interop"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/interop/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/jamie-bitflight/claude_skills/interop"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/interop.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.00060 | $0.02357 |
| Opus 5 | $0.00030 | $0.01179 |
| Sonnet 5 | $0.00012 | $0.00471 |
| Haiku 4.5 | $0.00006 | $0.00236 |
Grade A, and why
interop 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dh:interop — Superpowers Plan Interop Adapter
Routes a Superpowers plan file through the /work-backlog-item pipeline to produce a SAM task
plan, then writes back-references into the original plan. Does not re-implement any pipeline
logic — delegates entirely to /work-backlog-item.
The plan file path is provided as $ARGUMENTS.
Invocation: /dh:interop <path-to-plan-file>
Step 1 — Validate the argument
If $ARGUMENTS is empty, abort immediately:
ERROR: `/dh:interop` requires a path to a Superpowers plan file.
Usage: `/dh:interop docs/superpowers/plans/YYYY-MM-DD-slug.md`
Use the Read tool to open the file at the path given in $ARGUMENTS. If the file does not
exist or cannot be read, abort:
ERROR: Cannot read plan file: {path}
Make no changes to the file or backlog before this check passes.
Step 2 — Extract fields from the plan file
Extract the following fields by exact pattern match against the raw file text. No inference.
flowchart TD
Read([Raw file text in memory]) --> ExtractTitle[Extract Title<br>Pattern: first line matching ^# .+]
ExtractTitle --> HasTitle{Title found?}
HasTitle -->|No| AbortTitle["ABORT: Missing required field<br>ERROR: Plan file has no # heading — title is required"]
HasTitle -->|Yes| ExtractGoal[Extract Goal<br>Pattern: line matching ^\*\*Goal:\*\*\s*.+]
ExtractGoal --> HasGoal{Goal found?}
HasGoal -->|No| AbortGoal["ABORT: Missing required field<br>ERROR: Plan file has no **Goal:** field — goal is required"]
HasGoal -->|Yes| ExtractSpec[Extract Spec<br>Pattern: line matching ^\*\*Spec:\*\*\s*.+]
ExtractSpec --> HasSpec{Spec found?}
HasSpec -->|No| WarnSpec["Log warning: no **Spec:** field found — continuing"]
HasSpec -->|Yes| SpecOK[Spec captured]
WarnSpec --> ExtractBacklog
SpecOK --> ExtractBacklog[Extract Backlog item<br>Pattern: line matching ^\*\*Backlog item:\*\*\s*#\d+]
ExtractBacklog --> HasBacklog{Backlog item found?}
HasBacklog -->|Yes — integer N captured| ExtractChunks
HasBacklog -->|No| CreateBacklog[Step 3 — create backlog item]
CreateBacklog --> ExtractChunks
ExtractChunks[Extract Chunks<br>Pattern: all lines matching ^## Chunk \d+: .+] --> HasChunks{At least one chunk found?}
HasChunks -->|No| WarnChunks["Log warning: no ## Chunk N: headings found<br>Chunk annotation step will be skipped"]
HasChunks -->|Yes| ChunksOK[All chunk numbers and names captured]
WarnChunks --> Proceed([Proceed to Step 3])
ChunksOK --> Proceed
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 First seen · 225 lines · 60 tokens per session scan A da3b725661b7
interop is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 2,357 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.