discover-implementations

discover-implementations is a skill for Claude Code, Codex from Cratis/VerticalSlices. It costs 69 tokens per session (1,026 once invoked), scanned A, a copy of discover-implementations, MIT.

A guide for finding every implementation of a C# interface in a Cratis project. An implementation is a class that provides the behavior promised by an interface, such as a handler, validator, or strategy.

In plain words
What is it for?
Use it for dispatchers, filters, validators, formatters, strategies, providers, and resolvers that must discover multiple implementations, using `IInstancesOf<T>` and the required registration convention.
Why use it?
It removes manually maintained dependency-injection registrations when code needs to call or combine all implementations of an abstraction.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/cratis/verticalslices/discover-implementations
Any agent
npx skills add Cratis/VerticalSlices --skill discover-implementations
Clone the repo
git clone --depth 1 https://github.com/Cratis/VerticalSlices

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for discover-implementations

README.md
[![agentmods](https://agentmods.dev/badge/skills/cratis/verticalslices/discover-implementations.svg)](https://agentmods.dev/skills/cratis/verticalslices/discover-implementations)
Your own site
<a href="https://agentmods.dev/skills/cratis/verticalslices/discover-implementations"><img src="https://agentmods.dev/badge/skills/cratis/verticalslices/discover-implementations.svg" alt="Measured on agentmods" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,026 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00069 $0.01026
Opus 5 $0.00034 $0.00513
Sonnet 5 $0.00014 $0.00205
Haiku 4.5 $0.00007 $0.00103

Measured 4d ago against content hash 907a0f4f3d06, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

discover-implementations 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.

Origin

This is a copy

100% identical to discover-implementations — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.ai/skills/discover-implementations/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Wire convention-based discovery for a set of implementations behind an abstraction.

The pattern in one line

Inject IInstancesOf<TInterface> from Cratis.Types. Mark implementations with [Singleton]. Delete any services.AddSingleton<TInterface, Impl>() lines that registered them.

When this skill applies

The consumer of an abstraction needs to iterate, filter, or fan out to every registered implementation. Common shapes:

  • *Handlers, *Filters, *Validators, *Formatters, *Strategies, *Providers, *Resolvers — anything plural that delegates to a set.
  • A dispatcher that picks the right implementation by calling CanHandle(...) and forwarding to the matching one.
  • A composite that fans a single input out to all implementations and aggregates results.

When it does NOT apply

  • The consumer needs one implementation chosen at composition time → constructor-inject the concrete interface and let normal DI resolve IFoo → Foo.
  • The method returns a sequence of values to a caller → IEnumerable<T> (or IReadOnlyList<T>, etc.) is still the right return type. The rule is only about injecting implementations of an abstraction.

Step 1 — Confirm the implementations are discoverable

IInstancesOf<T> discovers types by convention from loaded assemblies. The only requirements:

  • Each implementation is a non-abstract public class.
  • It implements the interface directly (not via another layer that hides it).

No assembly attribute is needed — the Cratis framework's type discovery picks them up automatically.

Step 2 — Mark implementations as singletons (default)

[Singleton]
public class EventResultHandler(IEventTypes eventTypes) : IReactorSideEffectHandler
{
    public bool CanHandle(ReactorContext context, object value) => /* ... */;
    public Task Handle(ReactorContext context, object value) => /* ... */;
}

Add using Cratis; if [Singleton] is unresolved.

Skip [Singleton] only when the implementation must be transient — i.e. it holds per-call state that cannot be shared. The convention IFoo → Foo still applies for transients; do not register them explicitly.

Read the full file on GitHub · 96 lines

Changes

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.

  1. 4d ago First seen · 96 lines · 69 tokens per session scan A 907a0f4f3d06

Subscribe to this mod's changes

discover-implementations is a skill published in the GitHub repository Cratis/VerticalSlices (2 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 1,026 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to discover-implementations, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

cratis-command

Step-by-step guidance for creating a Cratis Arc command — [Command] record, Handle() method, CommandValidator, proxy generation, and React .use() hook with CommandDialog. Use when adding or creating a command, wiring up a form or button to the backend, working with IEventLog, CommandResult, CommandValidator…

Cratis/AI · 80 tokens

ship-changes

Ship staged or unstaged local changes: create a branch, make logical commits, push to origin, open a PR with the correct description and label, merge it, prepare no-effect dispositions for related issues, and delete the branch locally and on origin. Use whenever the user asks to commit, push, create a PR, ship, or…

Cratis/AI · 74 tokens

auth-and-identity

Use this skill for authentication, authorization, or identity in a Cratis Arc project — backend, frontend, or both. Covers identity providers (IProvideIdentityDetails), protecting commands/queries with authorization attributes, Microsoft Identity Platform, connecting backend identity to React, multi-tenant identity…

Cratis/AI · 88 tokens

cratis-react-page

Step-by-step guidance for building a React page in a Cratis Arc application — DataPage lists, CommandDialog toolbar actions, confirmation and busy-indicator dialogs, row selection, details components, observable queries, and MVVM. Use when building or modifying a page that lists/displays data, adding a table, wiring…

Cratis/AI · 93 tokens

cratis-readmodel

Step-by-step guidance for creating a Cratis Chronicle read model from scratch — defining events, choosing between projection and reducer, [ReadModel] record with static query methods, and the generated TypeScript proxy in React. Use when creating a read model, working with [EventType], [ReadModel], IProjectionFor…

Cratis/AI · 100 tokens

toolbar

Use this skill when asked to add or build a canvas-style icon toolbar using the @cratis/components Toolbar component. Covers Toolbar, ToolbarButton, ToolbarSeparator, ToolbarSection, ToolbarContext, and ToolbarFanOutItem. Use whenever building tool panels, drawing tool selectors, zoom controls, or any icon-button…

Cratis/AI · 78 tokens