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 nezolder/civil3d-mcp-roslyn --skill road_design_readinessgit clone --depth 1 https://github.com/nezolder/civil3d-mcp-roslynWrote 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/nezolder/civil3d-mcp-roslyn/road_design_readiness)<a href="https://agentmods.dev/skills/nezolder/civil3d-mcp-roslyn/road_design_readiness"><img src="https://agentmods.dev/badge/skills/nezolder/civil3d-mcp-roslyn/road_design_readiness/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/nezolder/civil3d-mcp-roslyn/road_design_readiness"><img src="https://agentmods.dev/badge/skills/nezolder/civil3d-mcp-roslyn/road_design_readiness.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.00026 | $0.01037 |
| Opus 5.5 | $0.00010 | $0.00415 |
| Sonnet 5.5 | $0.00005 | $0.00207 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
road_design_readiness 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Template
var dbmod = Convert.ToInt32(
Autodesk.AutoCAD.ApplicationServices.Application.GetSystemVariable("DBMOD")
);
var buildNamedGroup = (Func<string, object> lookup, int total, string[] requiredNames) =>
{
var missing = new List<string>();
var sample = new List<string>();
foreach (var name in requiredNames)
{
var found = false;
try
{
var value = lookup(name);
found = value != null && (value is not ObjectId id || !id.IsNull);
}
catch
{
// A missing style can be reported without depending on a public name getter.
}
if (found)
{
if (sample.Count < 3) sample.Add(name);
}
else
{
missing.Add(name);
}
}
return new {
total,
required = requiredNames.Length,
missing,
ready = missing.Count == 0,
sample,
truncated = total > sample.Count
};
};
var buildMinimumGroup = (int total) =>
{
var missing = new List<string>();
if (total < 1) missing.Add("at least one style");
var sample = new List<string>();
return new {
total,
required = 1,
missing,
ready = total >= 1,
sample,
truncated = total > 0
};
};
var styles = CivilDoc.Styles;
var alignment = buildNamedGroup(
name => styles.AlignmentStyles[name],
styles.AlignmentStyles.Count,
new[] { "Tervező" }
);
var profile = buildNamedGroup(
name => styles.ProfileStyles[name],
styles.ProfileStyles.Count,
new[] { "Terep", "Tervező" }
);
var profileView = buildNamedGroup(
name => styles.ProfileViewStyles[name],
styles.ProfileViewStyles.Count,
new[] { "Út" }
);
var assembly = buildNamedGroup(
name => styles.AssemblyStyles[name],
styles.AssemblyStyles.Count,
new[] { "Szabványos" }
);
var codeSet = buildNamedGroup(
name => styles.CodeSetStyles[name],
styles.CodeSetStyles.Count,
new[] { "Nyomterv tervező", "Nyomterv KSZ nyomtatás" }
);
var corridor = buildMinimumGroup(styles.CorridorStyles.Count);
var sampleLine = buildNamedGroup(
name => styles.SampleLineStyles[name],
styles.SampleLineStyles.Count,
new[] { "Út mintavonal" }
);
var section = buildNamedGroup(
name => styles.SectionStyles[name],
styles.SectionStyles.Count,
new[] { "Meglévő terep", "Tervezett pálya" }
);
var sectionView = buildNamedGroup(
name => styles.SectionViewStyles[name],
styles.SectionViewStyles.Count,
new[] { "Út keresztszelvény rajz" }
);
var surface = buildNamedGroup(
name => styles.SurfaceStyles[name],
styles.SurfaceStyles.Count,
new[] { "Szabványos" }
);
var partsList = buildNamedGroup(
name => styles.PartsListSet[name],
styles.PartsListSet.Count,
new[] { "Szabványos" }
);
var superelevationView = buildMinimumGroup(styles.SuperelevationViewStyles.Count);
var groups = new {
alignment,
profile,
profileView,
assembly,
codeSet,
corridor,
sampleLine,
section,
sectionView,
surface,
partsList,
superelevationView
};
var readiness = new[] {
alignment.ready,
profile.ready,
profileView.ready,
assembly.ready,
codeSet.ready,
corridor.ready,
sampleLine.ready,
section.ready,
sectionView.ready,
surface.ready,
partsList.ready,
superelevationView.ready
};
return new {
overallReady = readiness.All(value => value),
dbmod,
groups
};
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.
- 28d ago First seen · 167 lines · 26 tokens per session scan A a681c4358183
road_design_readiness is a skill published in the GitHub repository nezolder/civil3d-mcp-roslyn (3 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 1,037 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.
Other skills, from other repositories
n8n-agents
Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain. AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-subworkflows
Build reusable, composable n8n sub-workflows. Use when extracting shared logic, building anything multi-step or reused across workflows, or any workflow over 10 nodes — and whenever the user mentions sub-workflows, Execute Workflow, reuse, shared/common logic, modular workflows, "Define Below" inputs…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-binary-and-data
Handle files and binary data in n8n correctly. Use when working with files, images, PDFs, attachments, uploads or downloads, base64, vision/multimodal input, or when an AI agent needs a file as tool input or output — and whenever the user mentions $binary, binaryPropertyName, "read the PDF", "attach the file", "send…
n8n-code-tool
Write JavaScript or Python for the n8n Custom Code Tool (@n8n/n8n-nodes-langchain.toolCode) — the AI-agent-callable tool, NOT the workflow Code node. Use when building a Code Tool attached to an AI Agent, writing code that an LLM will invoke, parsing the query input, returning a string result, defining an input schema…