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 Metalnib/dotnet-episteme-skills --skill dotnet-techne-cross-repo-impactgit clone --depth 1 https://github.com/Metalnib/dotnet-episteme-skillsWrote 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/metalnib/dotnet-episteme-skills/dotnet-techne-cross-repo-impact)<a href="https://agentmods.dev/skills/metalnib/dotnet-episteme-skills/dotnet-techne-cross-repo-impact"><img src="https://agentmods.dev/badge/skills/metalnib/dotnet-episteme-skills/dotnet-techne-cross-repo-impact/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/metalnib/dotnet-episteme-skills/dotnet-techne-cross-repo-impact"><img src="https://agentmods.dev/badge/skills/metalnib/dotnet-episteme-skills/dotnet-techne-cross-repo-impact.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.02979 |
| Opus 5 | $0.00048 | $0.01489 |
| Sonnet 5 | $0.00019 | $0.00596 |
| Haiku 4.5 | $0.00010 | $0.00298 |
Grade A, and why
dotnet-techne-cross-repo-impact 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 12d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Cross-Repo Impact Analysis
Procedural recipe for reviewing a .NET pull request against a multi-repo
microservice workspace: detect breaking changes, trace their blast radius
across repo boundaries, check for a compatible downstream PR, and render
a structured cross-repo-impact.md report.
This skill is procedural only. It does not describe agent identity, default stance, or severity philosophy — those belong in the consuming agent's system prompt. This skill tells the agent how to run the analysis when invoked.
Requirements
- Synopsis v1.6.0+ binary available, either:
- as a long-running MCP daemon (preferred — fastest, combined multi-repo graph kept warm), or
- as a CLI invoked per-run (one-shot mode, no daemon required).
Use the companion
dotnet-techne-synopsisskill to auto-download and detect the binary.
- git on the PATH for diff inspection.
- A code-host CLI on the PATH for compatible-PR search:
ghfor GitHub (authenticated, repo read).glabfor GitLab (authenticated, MR read).- Others acceptable if the agent's harness provides an equivalent
searchOpenPrstool.
- Read access to a workspace root that contains the PR repo AND every
other repo in the fleet as peer directories (Synopsis discovers repos
by
.gitmarkers under the root).
When to use this skill
Trigger this skill when a PR diff touches any of:
- Public types, methods, records, or interfaces in an assembly referenced by other projects.
- ASP.NET controllers, minimal-API endpoints, route constants, or HTTP verb attributes.
- EF Core entity classes,
DbContextoverrides,OnModelCreatingconfigurations,ToTable/HasColumnNamecalls, or migration files. - DTO classes or records carrying
[JsonPropertyName],[DataMember],[JsonConverter], or used asHttpClientrequest/response bodies. PackageReferenceelements in.csprojorDirectory.Packages.propswhere the package is also referenced by other repos.appsettings.jsonkeys that appear asConfigurationKeynodes in the Synopsis graph.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 300 lines · 95 tokens per session scan A e2736c582e9f
dotnet-techne-cross-repo-impact is a skill published in the GitHub repository Metalnib/dotnet-episteme-skills (12 stars, last pushed 3d ago), licensed MIT. It adds 95 tokens to every session and 2,979 once invoked, about $0.0005 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-30.
Other skills, from other repositories
resharper-clt
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…
roslynator
Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…
stylecop-analyzers
Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…
dotnet-best-practices
Ensure .NET/C# code follows maintainable, modern best practices. Use when reviewing or improving C# code, solution structure, async patterns, dependency injection, or testability.
cratis-engineering-csharp-conventions
Apply the Cratis C# house conventions when writing or reviewing C# in a Cratis repository - formatting, naming, records and primary constructors, nullable handling, XML documentation, custom exceptions, structured logging, dependency injection, and service lifetimes. Use for any "how should this be written" C# style…
quickdup
Use the open-source free QuickDup clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring candidates, or repeatable duplication. USE FOR: the repo wants QuickDup; the team needs repeatable duplicate-code scans for C#; the user asks about DRY…