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/nelson820125/iforgeai/dotnet-engineernpx skills add nelson820125/iforgeai --skill dotnet-engineergit clone --depth 1 https://github.com/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/dotnet-engineer)<a href="https://agentmods.dev/skills/nelson820125/iforgeai/dotnet-engineer"><img src="https://agentmods.dev/badge/skills/nelson820125/iforgeai/dotnet-engineer.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.00071 | $0.01883 |
| Opus 5 | $0.00036 | $0.00941 |
| Sonnet 5 | $0.00014 | $0.00377 |
| Haiku 4.5 | $0.00007 | $0.00188 |
Grade A, and why
dotnet-engineer 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output Language Rule
Read output_language from .ai/context/workflow-config.md. Write ALL deliverables and code comments in that language. If the file is absent or the field is unset, default to en-US.
DB Approach Rule
Read db_approach from .ai/context/workflow-config.md before starting any database-related implementation:
database-first(default when unset): The authoritative schema is defined in.ai/temp/db-init.sqlproduced by the DBA. You must implement ORM entity classes and repository code that matches this schema exactly. Do NOT usedotnet ef migrations addto initialise the database — the database is initialised from the DBA's SQL script.code-first: You are responsible for driving the schema through ORM migrations. Workflow:- Read
.ai/temp/db-design.md(DBA design document) as the reference for field types, constraints, indexes, and default values - Implement entity classes faithfully according to the design document
- Run
dotnet ef migrations add {MigrationName}to generate the migration - Run
dotnet ef database update(or equivalent) to apply it — this replacesdb-init.sql - Document each migration task in the WBS and work log with its migration name and purpose
- Read
Phase Mode
This skill operates in two modes depending on how it is invoked:
| Mode | Trigger | Task | Output |
|---|---|---|---|
/contract |
digital-team Phase 5a |
Define full API contract schemas in api-contract.md |
.ai/temp/api-contract.md (fully detailed, ready for frontend review) |
/develop (default) |
digital-team Phase 6b, or standalone invocation |
Implement backend code based on api-contract.md + wbs.md |
Source code + work log |
Contract mode (/contract) rules:
- Read
.ai/temp/api-contract.md(architect's skeleton) and.ai/temp/wbs.md - Fill in Request schema, Response schema, HTTP status codes, and validation rules for each endpoint
- Do NOT write implementation code in this mode — output is documentation only
- The completed contract is reviewed by the frontend engineer before development begins
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.
- 5d ago First seen · 149 lines · 0 tokens per session scan A b166e8eab5a6
dotnet-engineer is a skill published in the GitHub repository nelson820125/iforgeai (8 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,883 once invoked, about $0.0004 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
dotnet
.NET development environment. Use when the project needs this capability or the user / team manifest asks for it. Use for specialized dotnet work when listed in TEAM.yaml or explicitly requested.
dotnet-reverse
.NET / C# 二进制逆向。当目标是 .NET assembly（PE 头含 CLR、.exe/.dll 托管程序）、C# 编译产物（含 NativeAOT）、红队 Sharp 工具（Rubeus / SharpHound / SharpHound 等）、.NET 混淆程序（ConfuserEx / SmartAssembly / Babel / Eazfuscator）、.NET loader / info-stealer / 套壳 malware 时使用。优先用 dnSpyEx + de4dot，需要 AI 直接操作时联动 dnSpy MCP。不用于纯 native 二进制（走 reverse-engineering /…
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
agui-dotnet-wire-types
Add or modify a wire/protocol type in the AG-UI .NET SDK AGUI.Abstractions package — a new event, message, or content-part type, the AOT source-gen serializer context, or a polymorphic JSON converter, keeping it AOT-safe, JSON-wire-compatible with the TypeScript reference, and PublicAPI-clean. USE FOR: adding an AG-UI…
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…