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/stefanthecode/dotnet-ai-toolkit/modular-monolith-generatornpx skills add StefanTheCode/dotnet-ai-toolkit --skill modular-monolith-generatorgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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/stefanthecode/dotnet-ai-toolkit/modular-monolith-generator)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/modular-monolith-generator"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/modular-monolith-generator.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.00105 | $0.00762 |
| Opus 5 | $0.00053 | $0.00381 |
| Sonnet 5 | $0.00021 | $0.00152 |
| Haiku 4.5 | $0.00011 | $0.00076 |
Grade A, and why
modular-monolith-generator 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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modular Monolith Generator
Set up (or tighten) a modular monolith: each module owns its domain, exposes a small public contract, keeps everything else internal, and talks to other modules through contracts or an in-process bus — so you get module independence without microservice overhead.
Input — point it at your project
Works on a target: a file, folder, project/solution, or GitHub URL. If modules exist, audit their boundaries; if not, propose a split. Detect with: find <target> -name "*.csproj" and grep -rn "public class\|internal class" --include=*.cs <target> | head.
Module layout
src/
├── Modules/
│ ├── Orders/
│ │ ├── Orders.Public/ # contracts other modules may use (DTOs, integration events, a façade interface)
│ │ └── Orders/ # internal: domain, handlers, EF — internal by default
│ ├── Billing/
│ │ ├── Billing.Public/
│ │ └── Billing/
├── Shared/ # truly shared kernel only (Result, base types)
└── Host/ # composition root: wires every module
Module registration (self-contained)
public interface IModule
{
IServiceCollection RegisterModule(IServiceCollection services, IConfiguration config);
void MapEndpoints(IEndpointRouteBuilder app);
}
// Host discovers and calls every IModule — no module references another module's internals.
Boundaries — enforce them, don't just hope
- A module references only other modules'
.Publicprojects, never their internals. - Cross-module calls go through a public façade interface or integration events on an in-process bus (MediatR notifications, or a channel) — not direct DB access into another module's tables.
- One schema per module (or clearly owned tables); no foreign keys across module boundaries.
Guardrail test (NetArchTest)
[Fact]
public void Orders_internals_are_not_referenced_by_other_modules()
{
var result = Types.InAssembly(typeof(BillingModule).Assembly)
.Should().NotHaveDependencyOn("Company.Modules.Orders") // internal assembly
.GetResult();
Assert.True(result.IsSuccessful);
}
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.
- 4d ago First seen · 64 lines · 105 tokens per session scan A 07c605c77103
modular-monolith-generator is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 25d ago), licensed MIT. It adds 105 tokens to every session and 762 once invoked, about $0.0005 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
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
csv-to-sif
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.
modular-skills
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
site-history
Neighborhood context and history — adjacent uses, architectural character, landmarks, commercial activity, and planned development from an address. Use when the user asks about a site's history or surroundings, "what's around this site", neighborhood character, or nearby planned development.