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/fpindej/netrock/add-options-classnpx skills add fpindej/netrock --skill add-options-classgit clone --depth 1 https://github.com/fpindej/netrockWrote 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/fpindej/netrock/add-options-class)<a href="https://agentmods.dev/skills/fpindej/netrock/add-options-class"><img src="https://agentmods.dev/badge/skills/fpindej/netrock/add-options-class.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.00009 | $0.00283 |
| Opus 5 | $0.00005 | $0.00142 |
| Sonnet 5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
add-options-class 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.
What it actually says
Adds a typed options/configuration class.
Steps
- Create in the appropriate layer:
- Infrastructure:
src/backend/MyProject.Infrastructure/{Area}/Options/{Name}Options.cs - WebApi:
src/backend/MyProject.WebApi/Options/{Name}Options.cs
- Infrastructure:
- Structure:
/// <summary> /// Configuration for {area}. Maps to "{SectionName}" in appsettings.json. /// </summary> public sealed class {Name}Options { public const string SectionName = "{Section}"; /// <summary> /// Gets or sets the ... /// </summary> [Required] public string Value { get; init; } = string.Empty; } - Add section to
appsettings.json(andappsettings.Development.jsonif dev differs - dev/test appsettings excluded from production publish viaStripDevConfig) - Register in DI extension:
services.AddOptions<{Name}Options>() .BindConfiguration({Name}Options.SectionName) .ValidateDataAnnotations() .ValidateOnStart(); - Update
docs/before-you-ship.mdif this is a must-configure production setting
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 · 38 lines · 9 tokens per session scan A d9a5b6f8828c
add-options-class is a skill published in the GitHub repository fpindej/netrock (231 stars, last pushed 6d ago), licensed MIT. It adds 9 tokens to every session and 283 once invoked, about $0.0000 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
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
creating-dotnet-mcp-servers
Use when building Model Context Protocol (MCP) servers in .NET, configuring tools, transports (SSE/stdio), JSON serialization for AOT, or testing MCP endpoints.
update-dependencies
Use when the task in front of you is to move dependency pins — packages in either stack, Rust crates, tools, SDKs, GitHub Action references, or container images — or to find out which of them are behind and whether any changed licence.
api-design
Guidelines for RESTful API design, endpoint naming conventions, and standardizing JSON responses.
python
Enforces FastAPI, Dependency Injection, and general Python coding standards based on the repository structure.
react
Guidelines for the React frontend, TanStack ecosystem, and React 19 standards. Use when modifying the UI.