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 sk-pipeline-pathsgit 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/sk-pipeline-paths)<a href="https://agentmods.dev/skills/gustavo-meilus/superpipelines/sk-pipeline-paths"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/sk-pipeline-paths/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/sk-pipeline-paths"><img src="https://agentmods.dev/badge/skills/gustavo-meilus/superpipelines/sk-pipeline-paths.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.00055 | $0.03504 |
| Opus 5.5 | $0.00022 | $0.01402 |
| Sonnet 5.5 | $0.00011 | $0.00701 |
| Haiku 4.5 | $0.00006 | $0.00350 |
Grade A, and why
sk-pipeline-paths 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 1mo 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Path Resolver — Scope-Aware Layout
Data Root & Git Integration
Generated pipelines (v2.x+) are data under the single tier-independent data root
(RESOLVE_DATA_ROOT); the per-tier scope roots below are legacy/materialization only.
<data_roots_table>
| Scope | Physical Root | Git Status | Persistence |
|---|---|---|---|
| Project | <workspace>/.superpipelines/ |
Committed | Shared with the team. |
| Local | <workspace>/.superpipelines/ |
Ignored | Machine-specific/temporary. |
| User | ~/.superpipelines/ |
External | Global across all workspaces. |
| </data_roots_table> |
Per-Tier Scope Roots (legacy back-compat reads + native materialization target)
These per-tier roots no longer locate generated pipeline data (see Data Root above). They are
consumed only by (a) ENUMERATE_ALL_SCOPE_ROOTS read-only legacy back-compat and (b) sk-platform-dispatch
MATERIALIZE, which writes the ephemeral native agent file into the host's own dir.
<scope_roots_per_tier>
| Tier | Workspace root | User root |
|---|---|---|
| Tier 1 (CC) | <workspace>/.claude/ |
~/.claude/ |
| Tier 1b (OC) | <workspace>/.opencode/ |
~/.opencode/ |
| Tier 1c (Antigravity) | <workspace>/.agents/antigravity/ |
~/.antigravity/ |
| Tier 1d (Codex) | <workspace>/.codex/ |
~/.codex/ |
| Tier 2 (Cursor/Windsurf/Cline) | <workspace>/.superpipelines/ |
~/.superpipelines/ |
| </scope_roots_per_tier> |
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.
- 1mo ago First seen · 235 lines · 55 tokens per session scan A 03b41b3cad84
sk-pipeline-paths is a skill published in the GitHub repository gustavo-meilus/superpipelines (4 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 3,504 once invoked, about $0.0002 per session on Opus 5.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
agentrq
Execute tasks assigned by humans or supervisor agents within a specific AgentRQ workspace. Use when you receive channel messages or need to report progress on tasks.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
github-triage
Triage GitHub issues through a label-based state machine with interactive grilling sessions. Use when user wants to triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
plan
Breaks features/goals into phased plans with task lists, agent assignments, dependencies. Triggers: plan feature, implementation roadmap, break down task, project phases.
write-a-prd
Creates PRD via interactive interview + codebase exploration + module design. Triggers: write PRD, product requirements, plan new feature, PRD interview.
swarm-orchestration
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.