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-fgit 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-f)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/run-parity-test-f"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-f/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-f"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-f.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.02482 |
| Opus 5 | $0.00022 | $0.01241 |
| Sonnet 5 | $0.00009 | $0.00496 |
| Haiku 4.5 | $0.00004 | $0.00248 |
Grade A, and why
run-parity-test-f 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-parity-test-f — Entry Skill
Entry point for the
parity-test-fpipeline. Orchestrates the sequential dispatch ofanalyzer,reviewer, andreporteragents on Tier 1d (Codex CLI) via model_driven dispatch.
Platform Context
- Tier:
tier_1d(Codex CLI) - Dispatch mechanism:
model_driven— the host orchestrator drives subagent sequencing; noTask()primitive available. - model_field_format:
toml_split— agents declaremodelandmodel_reasoning_effortin their TOML files; the entry skill does NOT stamp model fields into dispatch prompts. - Degradation warnings: None for Tier 1d.
Workflow
PHASE 0: PREFLIGHT
- Resolve
{ROOT}viask-pipeline-paths(scope root resolved from the active tier profile at runtime — never hardcode.codex/or any platform path). - Resolve
{runId}= ISO-8601 compact timestamp (e.g.,20260526T143000Z). - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-f/{runId}/. - Create
output/directory if absent:{ROOT}/output/. - Initialize
pipeline-state.jsonat{ROOT}/superpipelines/temp/parity-test-f/{runId}/pipeline-state.json:
{
"pipeline_id": "parity-test-f",
"run_id": "{runId}",
"started_at": "{iso8601}",
"plugin_version": "2.0.0",
"pattern": "1",
"status": "running",
"current_phase": 0,
"metadata": {
"source_tier": "tier_1d",
"runtime_tier": "tier_1d",
"model_field_format": "toml_split",
"resolved_models": {
"analyzer": "gpt-5.4-mini",
"reviewer": "gpt-5.5",
"reporter": "gpt-5.4-mini"
}
},
"phases": [
{
"index": 0,
"step_id": "analyzer",
"name": "analyze",
"status": "pending",
"agent": "agents/superpipelines/parity-test-f/analyzer.toml",
"outputs": [],
"error": null
},
{
"index": 1,
"step_id": "reviewer",
"name": "review",
"status": "pending",
"agent": "agents/superpipelines/parity-test-f/reviewer.toml",
"outputs": [],
"error": null
},
{
"index": 2,
"step_id": "reporter",
"name": "report",
"status": "pending",
"agent": "agents/superpipelines/parity-test-f/reporter.toml",
"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 · 189 lines · 44 tokens per session scan A d04979214cb7
run-parity-test-f 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,482 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
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-review-patterns
Multi-dimensional code assessment across security, quality, performance, and maintainability with confidence-gated reporting (>=80%) and Router Contract generation.
code-review-pipeline
Multi-dimensional code review across correctness, security, performance, and maintainability with confidence-gated reporting and remediation loops.
verification
Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current session. Dispatches fresh subagent per task.