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-dgit 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-d)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/run-parity-test-d"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-d/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-d"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/run-parity-test-d.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.00041 | $0.01511 |
| Opus 5 | $0.00020 | $0.00756 |
| Sonnet 5 | $0.00008 | $0.00302 |
| Haiku 4.5 | $0.00004 | $0.00151 |
Grade A, and why
run-parity-test-d 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.
This is a copy
91% identical to run-parity-test-c — 66 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
run-parity-test-d — Entry Skill
Entry point for the
parity-test-dpipeline. Orchestrates the sequential dispatch ofscannerandreporteragents on Tier 1c (Antigravity CLI) via model_driven dispatch.
Platform Context
- Tier:
tier_1c(Antigravity CLI) - Dispatch mechanism:
model_driven— the host orchestrator drives subagent sequencing; noTask()primitive available. - model_field_format:
omit— agents do not declaremodel:ormodel_tier:in their dispatch prompts; the host owns model selection. - Degradation warning (MUST surface before execution):
"Antigravity uses dynamic subagents — per-step model assignment is not supported. Only the orchestrator's model tier is user-configurable. Subagent model selection is owned by Antigravity's orchestrator."
Workflow
PHASE 0: PREFLIGHT
- Emit the Tier 1c degradation warning above.
- Resolve
{ROOT}viask-pipeline-paths(scope root resolved from the active tier profile at runtime — never hardcoded). - Resolve
{runId}= ISO-8601 timestamp (e.g.,20260526T143000Z). - Create temp directory:
{ROOT}/superpipelines/temp/parity-test-d/{runId}/. - Create
output/directory if absent:{ROOT}/output/. - Initialize
pipeline-state.jsonat{ROOT}/superpipelines/temp/parity-test-d/{runId}/pipeline-state.json:
{
"pipeline_id": "parity-test-d",
"run_id": "{runId}",
"started_at": "{iso8601}",
"plugin_version": "2.0.0",
"pattern": "1",
"status": "running",
"current_phase": 0,
"metadata": {
"source_tier": "tier_1c",
"runtime_tier": "tier_1c",
"orchestrator_tier": "fast",
"resolved_models": {}
},
"phases": [
{
"index": 0,
"step_id": "scanner",
"name": "scan",
"status": "pending",
"agent": "agents/superpipelines/parity-test-d/scanner.md",
"outputs": [],
"error": null
},
{
"index": 1,
"step_id": "reporter",
"name": "report",
"status": "pending",
"agent": "agents/superpipelines/parity-test-d/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 · 140 lines · 41 tokens per session scan A b10592a19ba6
run-parity-test-d is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,511 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to run-parity-test-c, differing in 66 lines, and is treated as a copy.
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.