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-bgit 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-b)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/run-parity-test-b"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-b/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-b"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-b.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.00044 | $0.02173 |
| Opus 5 | $0.00022 | $0.01086 |
| Sonnet 5 | $0.00009 | $0.00435 |
| Haiku 4.5 | $0.00004 | $0.00217 |
Grade A, and why
run-parity-test-b 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-parity-test-b — Entry Skill
Entry point for the
parity-test-bpipeline. Orchestrates the sequential Task()-based dispatch of theanalyzer,reviewer, andreporteragents on Tier 1 (Claude Code). The reviewer runs with worktree isolation +permissionMode: plan+disallowedTools: Write, Edit, Bash— structural write/review isolation.
Platform Context
- Tier:
tier_1(Claude Code) - Dispatch mechanism:
native_task—DISPATCH(mode="task", agent="{name}", isolation="worktree", context={...}). - model_field_format:
shorthand—model_tierin each agent's YAML frontmatter; resolver maps to concrete model. - Reviewer isolation:
structural—permissionMode: plan+disallowedTools: Write, Edit, Bash+ separate worktree. - Degradation warnings: None for Tier 1.
Workflow
PHASE 0: PREFLIGHT
- Resolve
{ROOT}viask-pipeline-paths. - Resolve
{runId}= ISO-8601 compact timestamp. - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-b/{runId}/. - Create
output/directory if absent:{ROOT}/output/. - If the user has not supplied the path to the input JSON file, ask for it now. Record as
{INPUT_PATH}. - Initialize
pipeline-state.jsonat{ROOT}/superpipelines/temp/parity-test-b/{runId}/pipeline-state.json:
{
"pipeline_id": "parity-test-b",
"run_id": "{runId}",
"started_at": "{iso8601}",
"plugin_version": "2.0.0",
"pattern": "1",
"status": "running",
"current_phase": 0,
"metadata": {
"source_tier": "tier_1",
"runtime_tier": "tier_1",
"model_field_format": "shorthand",
"resolved_models": {
"analyzer": "claude-haiku-4-5-20251001",
"reviewer": "claude-sonnet-4-6",
"reporter": "claude-haiku-4-5-20251001"
}
},
"phases": [
{
"index": 0,
"step_id": "analyzer",
"name": "analyze",
"status": "pending",
"agent": "agents/superpipelines/parity-test-b/analyzer.md",
"outputs": [],
"error": null
},
{
"index": 1,
"step_id": "reviewer",
"name": "review",
"status": "pending",
"agent": "agents/superpipelines/parity-test-b/reviewer.md",
"reviewer_isolation": "structural",
"outputs": [],
"error": null
},
{
"index": 2,
"step_id": "reporter",
"name": "report",
"status": "pending",
"agent": "agents/superpipelines/parity-test-b/reporter.md",
"outputs": [],
"error": null
}
]
}
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 · 195 lines · 44 tokens per session scan A b7e3263bf470
run-parity-test-b is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 2,173 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
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.