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 zdanovichnick/dotnet-pilot --skill convention-learnergit clone --depth 1 https://github.com/zdanovichnick/dotnet-pilotWrote 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/zdanovichnick/dotnet-pilot/convention-learner)<a href="https://agentmods.dev/skills/zdanovichnick/dotnet-pilot/convention-learner"><img src="https://agentmods.dev/badge/skills/zdanovichnick/dotnet-pilot/convention-learner.svg" alt="Measured on agentmods" 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.00038 | $0.01423 |
| Opus 5 | $0.00019 | $0.00711 |
| Sonnet 5 | $0.00008 | $0.00285 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
convention-learner 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 7d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convention Learner
Purpose: prevent naming drift. Generated code that doesn't match the project's conventions creates review friction and merge noise long after it ships.
Run this the first time you create a file in a codebase you haven't touched this session, and whenever the request leaves naming or structure open. Skip it when the request specifies the conventions, or when you already established them earlier in this conversation.
Detection
Six questions. Answer the ones your change actually depends on — a new validator needs the naming and folder answers, not the EF configuration one.
Step 1 — Naming Suffix Convention
What suffix does this project use for its handlers/services?
Grep pattern: "class \w+(Handler|Service|Manager|Controller|UseCase|Interactor)"
Files: src/**/*.cs
Determine: Handler, Service, Manager, Controller, or a mix?
If mixed: use the suffix most common in the feature area you're working in (e.g., if Orders/ uses Handler, use Handler for new order code even if Customers/ uses Service).
Step 2 — Folder / Architecture Style
What is the top-level organization under src/?
Glob: src/**/*.cs → inspect top-level directory names under src/<AppName>/
| Pattern found | Architecture style |
|---|---|
Features/<Feature>/<Action>/ |
Vertical Slice (VSA) |
Controllers/ + Services/ + Models/ |
Layered / MVC |
Domain/ + Application/ + Infrastructure/ |
Clean Architecture |
Domain/ + aggregates with AggregateRoot |
DDD |
Step 3 — DI Registration Pattern
How are services registered?
Grep pattern: "AddScoped|AddTransient|AddSingleton"
Files: src/**/*.cs
| Pattern found | Convention |
|---|---|
services.Add*(...) in Program.cs only |
Inline registration |
services.AddOrders() in extension methods |
Extension method per module/feature |
services.AddApplication() + services.AddInfrastructure() |
Layer-scoped extension methods |
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.
- 7d ago First seen · 146 lines · 38 tokens per session scan A 9f008539fe0a
convention-learner is a skill published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 11d ago), licensed MIT. It adds 38 tokens to every session and 1,423 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
architecture-refiner
Facilitate a structured conversation to define architecture principles for a repository. Supports multiple architecture styles: clean architecture (default), hexagonal / ports & adapters, modular monolith, or custom. Produces a formal architecture document that the corresponding atom will use. Use when setting up a…
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.