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/specification-pattern-generatornpx skills add StefanTheCode/dotnet-ai-toolkit --skill specification-pattern-generatorgit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWhat 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.00102 | $0.00789 |
| Opus 5 | $0.00051 | $0.00394 |
| Sonnet 5 | $0.00020 | $0.00158 |
| Haiku 4.5 | $0.00010 | $0.00079 |
Grade A, and why
specification-pattern-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 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Pattern Generator
Turn repeated query criteria into reusable, unit-testable Specification objects, with an evaluator that applies them to an EF IQueryable.
Input — point it at your code
Works on a target: a folder, project, or GitHub URL. Spot duplicated query logic to consolidate: grep -rn "\.Where(\|\.Include(\|\.OrderBy" --include=*.cs <target>.
Base specification
public abstract class Specification<T>
{
public Expression<Func<T, bool>>? Criteria { get; protected set; }
public List<Expression<Func<T, object>>> Includes { get; } = new();
public Expression<Func<T, object>>? OrderBy { get; private set; }
public int? Take { get; private set; }
public int? Skip { get; private set; }
public bool AsNoTracking { get; private set; } = true;
protected void Where(Expression<Func<T, bool>> c) => Criteria = c;
protected void Include(Expression<Func<T, object>> i) => Includes.Add(i);
protected void Order(Expression<Func<T, object>> o) => OrderBy = o;
protected void Page(int skip, int take){ Skip = skip; Take = take; }
protected void Tracked() => AsNoTracking = false;
}
Evaluator
public static class SpecificationEvaluator
{
public static IQueryable<T> Apply<T>(IQueryable<T> q, Specification<T> spec) where T : class
{
if (spec.AsNoTracking) q = q.AsNoTracking();
if (spec.Criteria is not null) q = q.Where(spec.Criteria);
q = spec.Includes.Aggregate(q, (cur, inc) => cur.Include(inc));
if (spec.OrderBy is not null) q = q.OrderBy(spec.OrderBy);
if (spec.Skip is not null) q = q.Skip(spec.Skip.Value);
if (spec.Take is not null) q = q.Take(spec.Take.Value);
return q;
}
}
Example spec + usage
public class ActiveOrdersForCustomer : Specification<Order>
{
public ActiveOrdersForCustomer(Guid customerId)
{
Where(o => o.CustomerId == customerId && o.Status == OrderStatus.Active);
Include(o => o.Lines);
Order(o => o.CreatedAt);
}
}
var orders = await SpecificationEvaluator
.Apply(db.Orders, new ActiveOrdersForCustomer(id)).ToListAsync(ct);
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 · 75 lines · 102 tokens per session scan A 41e1964a9635
specification-pattern-generator is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 23d ago), licensed MIT. It adds 102 tokens to every session and 789 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…