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 skills add NoesisVision/nasde-toolkit --skill tactical-dddgit clone --depth 1 https://github.com/NoesisVision/nasde-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/noesisvision/nasde-toolkit/tactical-ddd)<a href="https://agentmods.dev/skills/noesisvision/nasde-toolkit/tactical-ddd"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/tactical-ddd/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/noesisvision/nasde-toolkit/tactical-ddd"><img src="https://agentmods.dev/badge/skills/noesisvision/nasde-toolkit/tactical-ddd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00070 | $0.04523 |
| Opus 5.5 | $0.00028 | $0.01809 |
| Sonnet 5.5 | $0.00014 | $0.00905 |
| Haiku 4.5 | $0.00007 | $0.00452 |
Grade A, and why
tactical-ddd 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 1mo 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 — 549 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tactical DDD
Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design.
This codebase's conventions
This codebase targets .NET 8. It originated on an old .NET version and is being modernized as it is enriched — write idiomatic modern C#, do not copy the legacy style:
- File-scoped namespaces (
namespace Foo;), not bracketed blocks. - Value objects as
record/readonly record struct— you get value equality,ToString, and immutability for free, so do NOT hand-rollEquals/GetHashCode. Useinit-only /requiredmembers and a static factory (or a validating primary constructor) so an instance cannot exist in an invalid state. EF Core maps these via owned types / value converters — keep a way for EF to materialize them, but don't let EF needs dictate a mutable, ctor-less data bag. - Nullable reference types enabled; use them to make "must exist" vs "may be absent" explicit rather than relying on runtime null checks.
- Invariants: throw a domain-specific exception (or return a result type) from the factory /
method that enforces them — not a generic
Exception, and not validation scattered in services. - Layers:
Domain/(entities, value objects, invariants),Application/(services that orchestrate),Controllers/(HTTP + DTOs),Infrastructure/(EF Core config). Domain holds no EF or ASP.NET references. - Keep the public API (controllers, DTOs, endpoints) unchanged when refactoring internals.
Principles
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.
- 1mo ago First seen · 549 lines · 70 tokens per session scan A 97bfe32fb90d
tactical-ddd is a skill published in the GitHub repository NoesisVision/nasde-toolkit (14 stars, last pushed 10d ago), licensed MIT. It adds 70 tokens to every session and 4,523 once invoked, about $0.0003 per session on Opus 5.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-reviewer
Performs comprehensive code reviews with security, quality, and best practice checks.
code-reviewer
A skill that helps review code for best practices, bugs, and security issues.
api-contracts
API design and contract engineering — REST resource modelling, error envelopes, pagination, filtering, idempotency, versioning and deprecation, rate limiting, webhooks, OpenAPI, GraphQL schema and N+1 defence, and contract testing. Use when designing, reviewing or documenting an endpoint or integration; when the user…
performance-engineering
Performance engineering across the stack — Core Web Vitals (LCP, INP, CLS), bundle size and rendering strategy, image and font optimisation, backend latency budgets, caching layers, database query cost, profiling, and load testing. Use when the user says "slow", "performance", "optimize", "Core Web Vitals", "LCP"…
review-workflow-management
Read-only audit of the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) an app exposes for Dapr Workflows, with DWF-MGT-NNN findings. Use for "review workflow management" or "check workflow HTTP endpoints". To operate runs on Diagrid Catalyst use the catalyst-ai plugin.
review-pubsub-components
Reviews Dapr pub/sub configuration (components, Subscription files, resiliency, dapr.yaml and Aspire wiring) for inline secrets, unsecured brokers, dead-letter topics without retry policies, scopes and app-id or port collisions. Use for "review my pub/sub components" or "audit Dapr pubsub YAML".