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/managedcode/prompterone/dotnet-managedcode-storagenpx skills add managedcode/PrompterOne --skill dotnet-managedcode-storagegit clone --depth 1 https://github.com/managedcode/PrompterOneWhat 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.00045 | $0.00393 |
| Opus 5 | $0.00023 | $0.00197 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
dotnet-managedcode-storage 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dotnet-managedcode-storage — 88% identical, 2 lines differ
What it actually says
ManagedCode.Storage
Trigger On
- integrating
ManagedCode.Storageinto a .NET application - reviewing how a project abstracts file or object storage
- deciding whether to centralize storage provider differences behind one library
- documenting upload, download, container, or blob-handling flows with ManagedCode.Storage
Workflow
- Identify the actual storage use case:
- blob or file storage
- provider abstraction across environments
- app-service integration and configuration
- Verify whether the project wants one storage contract instead of provider-specific SDK calls scattered across the codebase.
- Keep application code dependent on the library abstraction, not directly on backend-specific storage SDKs unless a provider-only feature is truly required.
- Centralize provider configuration, credentials, and container naming in composition-root code and typed settings.
- Validate the real upload, download, existence-check, and deletion flows after wiring the library.
flowchart LR
A["Application service"] --> B["ManagedCode.Storage abstraction"]
B --> C["Provider-specific storage implementation"]
C --> D["Blob or object storage backend"]
Deliver
- concrete guidance on when ManagedCode.Storage is the right abstraction
- wiring guidance that keeps provider concerns out of business code
- verification steps for the storage flows the application actually uses
Validate
- the project really benefits from a storage abstraction and is not hiding provider-specific behavior it still needs
- storage configuration is centralized and explicit
- code reviews check real read and write paths, not only registration snippets
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.
- 2d ago First seen · 45 lines · 45 tokens per session scan A 419ed9d5d33c
dotnet-managedcode-storage is a skill published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 393 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
vela
Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…
widget-creator
Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.
aspire
Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost.…
blazorbindings-maui-third-party
Integrate third-party .NET MAUI control libraries into BlazorBindings.Maui apps by generating Razor wrappers, registering attached properties, and bridging to native elements for imperative APIs such as popups or bottom sheets. Use when adding, updating, or troubleshooting a MAUI control package in a…
nina-repository
Repository-specific guidance for working in the N.I.N.A. codebase and NINA.sln. Use when Codex is asked to modify, review, test, debug, navigate, or explain code in this repository; touch NINA. projects, app startup/DI, profiles/settings, localization, database migrations, equipment, astrometry, imaging, plate…
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…