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 aliengiraffe/vigilante --skill vigilante-issue-implementation-on-dotnetgit clone --depth 1 https://github.com/aliengiraffe/vigilanteWrote 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/aliengiraffe/vigilante/vigilante-issue-implementation-on-dotnet)<a href="https://agentmods.dev/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-dotnet"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-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/aliengiraffe/vigilante/vigilante-issue-implementation-on-dotnet"><img src="https://agentmods.dev/badge/skills/aliengiraffe/vigilante/vigilante-issue-implementation-on-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.00041 | $0.00759 |
| Opus 5.5 | $0.00016 | $0.00304 |
| Sonnet 5.5 | $0.00008 | $0.00152 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
vigilante-issue-implementation-on-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 1mo 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vigilante .NET Issue Implementation
Focus
- Read the prompt for detected tech stacks, process hints, and .NET security guidance before changing code.
- Follow the repository's existing .NET workflow, solution or project structure, analyzer configuration, and formatting conventions.
- Keep changes scoped to the issue and do not broaden into unrelated cleanup or package churn.
.NET Tooling Workflow
- Formatting: use the repository's established formatting path. When
dotnet formatis the standard SDK workflow, run it on the affected project or solution scope before committing. - Testing: run targeted
dotnet testfor the affected test project, project, or solution first, then broaden only when the change crosses project boundaries or the repository workflow requires it. - Analyzers: respect built-in .NET analyzers, nullable warnings,
.editorconfig,Directory.Build.props, and repo-defined warning severities. Do not weaken analyzer settings without a narrow, documented reason. - Package auditing: when dependency changes are involved or package risk is relevant, use the repository's standard NuGet restore or audit flow and review advisories when auditing is enabled.
- Dependencies: prefer framework or standard-library features when they cover the need. Avoid unrelated package version churn.
.NET Coding Style
- Follow existing project patterns for namespaces, file layout, and test structure.
- Preserve nullable reference type correctness and prefer explicit null handling over suppression.
- Prefer straightforward error handling and clear APIs over reflection-heavy or overly abstracted changes unless the issue requires it.
- Keep public API changes minimal and aligned with the issue.
Security
- Do not commit secrets, tokens, certificates, or environment-specific credentials.
- Prefer configuration binding, options patterns, environment variables, or local user-secrets workflows over hard-coded settings.
- In ASP.NET Core code, preserve secure defaults for authentication, authorization, antiforgery or CSRF protections where applicable, HTTPS, and sensitive-data handling.
- Respect security analyzers and dependency advisories when the repository enables them.
What ships with it
1 file 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.
- 1mo ago First seen · 44 lines · 41 tokens per session scan A 67f30633419e
vigilante-issue-implementation-on-dotnet is a skill published in the GitHub repository aliengiraffe/vigilante (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 759 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
agent-framework-builder-dotnet
Use this skill when building, modifying, reviewing, evaluating, integrating, or hosting .NET (C#) applications with Microsoft Agent Framework. Use it for Agent Framework agents, harness agents, workflows, orchestrations, declarative definitions, tools, sessions, middleware, evaluation, observability, integrations, or…
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
verify-dotnet-samples
How to build, run and verify the .NET sample projects in the Agent Framework repository. Use this when a user wants to verify that the samples still function as expected.
bmad-correct-course
Assess the impact of a significant change during sprint execution across the PRD, epics, architecture, and UX documents, and produce a sprint change proposal. Use when the user says "correct course" or "propose sprint change".
bmad-spec
Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: one kernel file plus supporting files that downstream skills build from. Also updates and validates existing specs. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec".
bmad-product-brief
Create, update, or validate a product brief. Use when the user wants help producing, editing, or validating a brief.