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 skills add gustavo-meilus/superpipelines --skill run-parity-test-igit clone --depth 1 https://github.com/gustavo-meilus/superpipelinesWrote 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/gustavo-meilus/superpipelines/run-parity-test-i)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/run-parity-test-i"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-i/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/gustavo-meilus/superpipelines/run-parity-test-i"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-i.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.00047 | $0.01943 |
| Opus 5 | $0.00023 | $0.00971 |
| Sonnet 5 | $0.00009 | $0.00389 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
run-parity-test-i 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 11d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-parity-test-i — Entry Skill
Entry point for the
parity-test-ipipeline. Orchestrates the sequential native-subagent dispatch of theinspectorandformatteragents on Tier 1b (OpenCode v1.15.10). Each step runs as a distinct subagent process — no inline execution, no Task() calls.
Platform Context
- Tier:
tier_1b(OpenCode v1.15.10) - Dispatch mechanism:
native_subagent—DISPATCH(mode="subagent", agent="{name}", context={...}). NOT Task(). NOT inline. - model_field_format:
provider_prefixed—model: opencode/big-pickledeclared in each agent's YAML frontmatter. - Reviewer isolation:
structural— each step runs in a distinct subagent process. - Degradation warnings: 1 active (see PHASE 0 below).
Workflow
PHASE 0: PREFLIGHT — DEGRADATION WARNING AND INITIALIZATION
Step 0.1 — Surface Tier 1b degradation warning (MANDATORY before any execution):
Surface the following warning to the user verbatim before any other action:
[Tier 1b Degradation Warning 1 of 1] Parallel fan-out (Pattern 2) degrades to sequential on OpenCode.
Step 0.2 — Resolve runtime context:
- Resolve
{ROOT}viask-pipeline-paths(scope root resolved from the active tier profile at runtime — NEVER hardcode.opencode/,.superpipelines/,.claude/, or any platform path). - Resolve
{runId}= ISO-8601 compact timestamp (e.g.,20260526T143000Z). - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-i/{runId}/. - Create
output/directory if absent:{ROOT}/output/.
Step 0.3 — Collect inputs:
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.
- 11d ago First seen · 169 lines · 47 tokens per session scan A e7c7056ec2d6
run-parity-test-i is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,943 once invoked, about $0.0002 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
moai-foundation-quality
TRUST 5 quality principles and how MoAI enforces them through agents, the 3-level harness, /moai gate, and sync-auditor scoring. Use for code review, quality gate checks, coverage targets, or TRUST 5 compliance.
quality-checklist
Validate implementation quality through custom checklists, scoring against constitution standards, specification coverage, and producing remediation recommendations.
orchestrated-execution
Execute work units through the rigorous 4-phase Metaswarm cycle (Implement -> Validate -> Adversarial Review -> Commit) with independent quality gate enforcement.
verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
check
Confirm a change before merge. /check verify drives the real app to prove behavior against the spec (every acceptance criterion met, every surface built). /check review runs a senior code review on a fresh model, one that did not write the code. Verify after /develop, review before a PR. Writes to docs/reviews/, never…
refactor
Refactors code for quality and maintainability. Triggers: refactor, clean up, restructure, improve code, modernize.