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 agentmods add skills/elbruno/graphify-dotnet/project-conventionsnpx skills add elbruno/graphify-dotnet --skill project-conventionsgit clone --depth 1 https://github.com/elbruno/graphify-dotnetWrote 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/elbruno/graphify-dotnet/project-conventions)<a href="https://agentmods.dev/skills/elbruno/graphify-dotnet/project-conventions"><img src="https://agentmods.dev/badge/skills/elbruno/graphify-dotnet/project-conventions.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 | $0.00012 | $0.00346 |
| Opus 5 | $0.00006 | $0.00173 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
project-conventions 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 4d 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
100% identical to project-conventions — 0 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.
What it actually says
Context
This is a starter template. Replace the placeholder patterns below with your actual project conventions. Skills train agents on codebase-specific practices — accurate documentation here improves agent output quality.
Patterns
[Pattern Name]
Describe a key convention or practice used in this codebase. Be specific about what to do and why.
Error Handling
Testing
Code Style
File Structure
Examples
// Add code examples that demonstrate your conventions
Anti-Patterns
- [Anti-pattern] — Explanation of what not to do and why.
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.
- 4d ago First seen · 57 lines · 12 tokens per session scan A 5feb0b864a03
project-conventions is a skill published in the GitHub repository elbruno/graphify-dotnet (90 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to project-conventions, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
roslyn-codelens
Use when working with any .NET / C# code (.cs/.csproj/.sln/.slnx files), finding callers/references/implementations, checking compiler errors or warnings, running dotnet build for diagnostics, searching for a type/method/interface by name, inspecting DI registrations, detecting dead code or circular dependencies…
roz-csharp-editing
Breakage-prevention rules for editing C# with the roz MCP server. Use before renaming a C# symbol, deleting or removing a C# symbol, or making a risky multi-file C# edit in a solution roz serves; also carries the recommended roz-mcp plugin permission block and per-project configuration.
dotnet-analyzer-actions
Perform code refactoring, generation, project file operations, decompilation, XAML analysis, and desktop pattern detection in .NET projects using Roslyn-powered MCP tools. Use when the user asks to refactor code, extract methods, rename symbols, generate code, implement interfaces, add project references, install…
dotnet-analyzer-code-intelligence
Navigate and understand C# code through symbol queries, type hierarchies, call graphs, and semantic analysis using Roslyn-powered MCP tools. Use when the user asks to find references, go to definition, understand type inheritance, explore call hierarchies, get symbol info, analyze code metrics, or traverse syntax…
dotnet-analyzer-code-quality
Detect code quality issues, architecture rule violations, code smells, technical debt, dead code, and performance problems in .NET projects using Roslyn-powered MCP tools. Use when the user asks to check code quality, detect code smells, measure technical debt, generate quality reports, check architecture rules, find…
dotnet-analyzer-project-analysis
Analyze .NET solution and project structure using Roslyn-powered MCP tools. Use when the user asks about solution structure, project dependencies, build order, file listing, code overview, or solution performance metrics. USE FOR: analyzing .sln/.slnx solution files, listing projects in a solution, getting project…