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 SebastienDegodez/copilot-instructions --skill setup-husky-dotnetgit clone --depth 1 https://github.com/SebastienDegodez/copilot-instructionsWrote 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/sebastiendegodez/copilot-instructions/setup-husky-dotnet)<a href="https://agentmods.dev/skills/sebastiendegodez/copilot-instructions/setup-husky-dotnet"><img src="https://agentmods.dev/badge/skills/sebastiendegodez/copilot-instructions/setup-husky-dotnet/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/sebastiendegodez/copilot-instructions/setup-husky-dotnet"><img src="https://agentmods.dev/badge/skills/sebastiendegodez/copilot-instructions/setup-husky-dotnet.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.00030 | $0.01399 |
| Opus 5 | $0.00015 | $0.00700 |
| Sonnet 5 | $0.00006 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
Grade A, and why
setup-husky-dotnet 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 9d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Husky Setup for .NET Projects (dotnet tool)
Install and configure Husky Git hooks for .NET projects using dotnet tool (not npm). Enforces conventional commit messages and code formatting via git hooks.
When to Use
- Setting up Git governance in .NET projects (new or existing)
- Enforcing team commit standards before they reach main branch
- Preventing unformatted code or invalid messages in version control
- REQUIRED BEFORE: First commits when governance is non-negotiable
When NOT to use: If .NET SDK unavailable, manually configure git hooks instead.
Critical: .NET Tool Only
Husky (dotnet tool) is pure .NET. Your environment needs:
.NET SDK 10.0+dotnetCLI available in PATHgitinitialized
No Node.js, npm, or JavaScript tools required.
Core Pattern
1. Create tool-manifest.json + install Husky dotnet tool
2. Enable git hook infrastructure with dotnet husky install
3. Create commit-msg hook that validates message format
4. Create pre-commit hook that runs dotnet-format
5. MANDATORY: Test hooks with both valid + invalid commits
6. Commit .husky/ and task-runner.json to git
Quick Reference
| Step | Command | Creates | Purpose |
|---|---|---|---|
| Setup | dotnet new tool-manifest |
.config/dotnet-tools.json |
Tool tracking |
| Install | dotnet tool install husky |
Adds Husky to tooling | Makes Husky available |
| Enable | dotnet husky install |
.husky/ directory |
Prepares git hook system |
| Msg Hook | dotnet husky add commit-msg |
Hook file | Validates commit format |
| Pre-Commit | dotnet husky add pre-commit |
Hook file | Runs formatting before commit |
Implementation
Prerequisites - VERIFY FIRST
CRITICAL - Run these commands NOW:
dotnet --version # Must return 6.0+
git --version # Must work
dotnet-format --version # Must be installed
If ANY fails, STOP — install missing tools before proceeding.
Required software:
- .NET SDK 6.0+ (download from dotnet.microsoft.com)
- Git repository initialized (
git initif needed) - dotnet-format global:
dotnet tool install -g dotnet.format
What ships with it
4 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.
- 9d ago First seen · 178 lines · 30 tokens per session scan A 25d520cab244
setup-husky-dotnet is a skill published in the GitHub repository SebastienDegodez/copilot-instructions (193 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,399 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-30.
Other skills, from other repositories
github-operations
WORKFLOW SKILL — Full GitHub contribution lifecycle: branches, conventional commits, issues, PRs, Actions, releases. gh CLI-first with MCP fallback. WHEN: "commit", "push", "open PR", "create branch", "create issue", "cut release", "GitHub operation". DO NOT USE FOR: Azure infrastructure, Bicep/Terraform code…
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
git-precommit
A pre-commit workflow that coordinates updates to project memory, documentation, changelogs, roadmaps, architecture notes, and commit messages before code is saved to Git.
git-doc-updater
A Git workflow that checks whether key project documentation still matches the code before a commit, push, or release.
commit-conventions
Standards for writing clear and consistent commit messages using Conventional Commits format. Use when making git commits, reviewing commit history, creating pull requests, or when the user asks about commit message formatting, git workflows, or version control best practices.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.