pipe_network_qc

pipe_network_qc is a skill for Claude Code, Codex from nezolder/civil3d-mcp-roslyn. It costs 19 tokens per session (994 once invoked), scanned A, original, MIT.

A Civil 3D checker for gravity pipe networks that looks for basic connection problems and pipe lengths that may be invalid.

In plain words
What is it for?
Use it to review selected or filtered pipe networks and receive a limited list of detected connection and length warnings.
Why use it?
It helps spot simple network issues without manually inspecting every pipe and structure.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review selected or filtered pipe networks and receive a limited list of detected connection and length warnings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc
Install

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.

Any agent
npx skills add nezolder/civil3d-mcp-roslyn --skill pipe_network_qc
Clone the repo
git clone --depth 1 https://github.com/nezolder/civil3d-mcp-roslyn

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for pipe_network_qc

README.md
[![agentmods](https://agentmods.dev/badge/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc/github.svg)](https://agentmods.dev/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc)
Your own site
<a href="https://agentmods.dev/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc"><img src="https://agentmods.dev/badge/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc/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.

agentmods 80×15 button for pipe_network_qc

Your own site · 80×15
<a href="https://agentmods.dev/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc"><img src="https://agentmods.dev/badge/skills/nezolder/civil3d-mcp-roslyn/pipe_network_qc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 994 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00994
Opus 5.5 $0.00008 $0.00398
Sonnet 5.5 $0.00004 $0.00199
Haiku 4.5 $0.00002 $0.00099

Measured 28d ago against content hash 2fdb277a3263, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-02, from the pricing page.

Security

Grade A, and why

pipe_network_qc 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 28d 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.

skills/pipe_networks/pipe_network_qc.skill.md · 123 lines

How it starts

The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Template

var networkNameFilter = "";
var limit = 25;
var partLimit = 1000;
var issueLimit = 25;
if (limit < 1 || partLimit < 1 || issueLimit < 1)
    return new { error = "limits must be at least 1" };

var networks = new List<object>();
var total = 0;

foreach (ObjectId networkId in CivilDoc.GetPipeNetworkIds())
{
    var network = Transaction.GetObject(networkId, OpenMode.ForRead) as Network;
    if (network == null) continue;
    if (!string.IsNullOrWhiteSpace(networkNameFilter)
        && !network.Name.Equals(networkNameFilter, StringComparison.OrdinalIgnoreCase))
        continue;

    total++;
    if (networks.Count >= limit) continue;

    var pipeIds = network.GetPipeIds();
    var structureIds = network.GetStructureIds();
    var issues = new List<object>();
    var issueCount = 0;
    Action<string, string, string, string> addIssue = (code, objectType, name, handle) => {
        issueCount++;
        if (issues.Count < issueLimit)
            issues.Add(new { code, objectType, name, handle });
    };

    var pipesInspected = 0;
    foreach (ObjectId pipeId in pipeIds)
    {
        if (pipesInspected >= partLimit) break;
        var pipe = Transaction.GetObject(pipeId, OpenMode.ForRead) as Pipe;
        if (pipe == null) continue;
        pipesInspected++;

        if (pipe.StartStructureId.IsNull)
            addIssue("PIPE_START_UNCONNECTED", "pipe", pipe.Name, pipe.Handle.ToString());
        if (pipe.EndStructureId.IsNull)
            addIssue("PIPE_END_UNCONNECTED", "pipe", pipe.Name, pipe.Handle.ToString());
        if (double.IsNaN(pipe.Length3D) || double.IsInfinity(pipe.Length3D) || pipe.Length3D <= 0)
            addIssue("PIPE_LENGTH_INVALID", "pipe", pipe.Name, pipe.Handle.ToString());
    }

    var structuresInspected = 0;
    foreach (ObjectId structureId in structureIds)
    {
        if (structuresInspected >= partLimit) break;
        var structure = Transaction.GetObject(structureId, OpenMode.ForRead) as Structure;
        if (structure == null) continue;
        structuresInspected++;

        if (structure.ConnectedPipesCount == 0)
            addIssue("STRUCTURE_DISCONNECTED", "structure", structure.Name, structure.Handle.ToString());
    }

    networks.Add(new {
        name = network.Name,
        handle = network.Handle.ToString(),
        partsList = network.PartsListId.IsNull ? null : network.PartsListName,
        referenceSurface = network.ReferenceSurfaceId.IsNull ? null : network.ReferenceSurfaceName,
        referenceAlignment = network.ReferenceAlignmentId.IsNull ? null : network.ReferenceAlignmentName,
        isReference = network.IsReferenceObject,
        isReferenceStale = network.IsReferenceStale,
        pipeCount = pipeIds.Count,
        pipesInspected,
        structureCount = structureIds.Count,
        structuresInspected,
        inspectionTruncated = pipeIds.Count > pipesInspected || structureIds.Count > structuresInspected,
        issueCountInInspectedParts = issueCount,
        issuesReturned = issues.Count,
        issuesTruncated = issueCount > issues.Count,
        issues
    });
}

return new {
    total,
    returned = networks.Count,
    truncated = total > networks.Count,
    limit,
    partLimit,
    issueLimit,
    networkNameFilter = string.IsNullOrWhiteSpace(networkNameFilter) ? null : networkNameFilter,
    networks
};

Read the full file on GitHub · 123 lines

Changes

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.

  1. 28d ago First seen · 123 lines · 19 tokens per session scan A 2fdb277a3263

Subscribe to this mod's changes

pipe_network_qc is a skill published in the GitHub repository nezolder/civil3d-mcp-roslyn (3 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 994 once invoked, about $0.0001 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-04.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens