SkillAgentSearch skills...

tiko-di

Compile-time orchestrator for Java 21+ — direct access, compile-time safe, nothing wrapped. Dependency injection + event bus ship in the core; you plug in HTTP, DB, cache, security via @Produces. Kotlin through Gradle + KSP2.

Install / Use

claude mcp add tomas-samek -- npx -y github:tomas-samek/tiko-di

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

83/100

Category

Security

Supported Platforms

Claude Code
Claude Desktop

Our assessment of tiko-di

tiko-di scores 83/100 on our quality scale, 879th of 1,098 Security skills we index.

Its MCP Server is 33 KB long, well organised into 29 sections with 4 code examples: a thorough specification that gives an agent plenty to work with.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated today, so tiko-di is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-11-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

tiko-di compared with similar skills

All 4 of these similar skills score higher than tiko-di; compare them before choosing.

SkillScoreStarsUpdatedFormat
tiko-di (this skill)by tomas-samek833todayMCP Server
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
hyperframesby heygen-com10088.2ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md

Frequently asked questions

How do I install tiko-di?
Run claude mcp add tomas-samek -- npx -y github:tomas-samek/tiko-di. The install tabs above show the steps for each supported agent.
Which AI agents does tiko-di work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is tiko-di safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is tiko-di still maintained?
The repository was last updated today, so tiko-di is actively maintained.
<picture> <source media="(prefers-color-scheme: dark)" srcset="https://tomas-samek.github.io/banners/dark/tiko-di.svg"> <img alt="tiko-di: Compile-time orchestrator for Java 21+" src="https://tomas-samek.github.io/banners/light/tiko-di.svg" width="100%"> </picture>

Tiko DI

A compile-time orchestrator for Java 21+: dependency injection and an event bus in the core, your libraries plugged in through @Produces

Maven Central Build Java Maven License Quality Gate Status Coverage

Website: tomas-samek.github.io/tiko-di · Status: on Maven Central (latest version in the badge above). Suitable for early-adopter experimentation. See docs/roadmap.md for what ships today and what's next.

🌐 More projects and writing: tomas-samek.github.io

What Tiko is

A compile-time orchestrator with an integrated event model and full compile-time validation.

Tiko orchestrates, it doesn't bundle — direct access, compile-time safe, nothing wrapped.

The container, the scopes, the event bus, and the wiring graph ship as the framework. HTTP servers, databases, caches, template engines, security libraries, and any other library — you bring directly, and tiko orchestrates the seam via @Produces. Nothing is wrapped or rewritten on the library side; nothing is re-invented on the framework side.

For the design principles behind it — three-layer architecture, event-pipeline trade-offs, and the direction it is headed — see docs/VISION.md.

Quick example

// 1. Define your components
@Component(scope = Scope.SINGLETON)
public class UserRepository {
    public User findById(String id) { /* ... */ return null; }
}

@Component(scope = Scope.SINGLETON)
public class UserService {
    private final UserRepository repository;

    @Inject
    public UserService(UserRepository repository) {
        this.repository = repository;
    }

    public User getUser(String id) {
        return repository.findById(id);
    }
}

// 2. Use the container
public class Main {
    public static void main(String[] args) {
        try (Container container = Tiko.create()) {
            UserService service = container.get(UserService.class);
            User user = service.getUser("123");
        }
    }
}

The annotation processor validates all dependencies at compile-time and generates the wiring code — plain Java you can read and step through. No reflection, no classpath scanning in your wiring.

Lifecycle & imperative publish. Tiko.create(...) returns an AutoCloseable container you manage (try-with-resources above). For a long-lived process — an HTTP service, a Kafka consumer, a scheduler — use Tiko.daemon(...) (it installs a graceful-shutdown hook so @PreDestroy runs on Ctrl+C / SIGTERM) and keep the process alive with the one canonical idiom daemon.awaitShutdown(); an HTTP server is a component the container starts and stops (HTTP cookbook). To publish events imperatively from inside a component, inject EventBus as a constructor dependency — it is built-in, no plain-class workaround. Details: the tiko-build skill and events.md.

Installation

Tiko ships to Maven Central. Import the BOM once — then declare the artifacts (and the annotation-processor path) without restating the version:

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>io.github.tomas-samek</groupId>
            <artifactId>tiko-bom</artifactId>
            <version>0.7.0</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependencies>
    <dependency>
        <groupId>io.github.tomas-samek</groupId>
        <artifactId>tiko-api</artifactId>
    </dependency>
    <dependency>
        <groupId>io.github.tomas-samek</groupId>
        <artifactId>tiko-runtime</artifactId>
    </dependency>
    <!-- Optional, only if you use @Configuration -->
    <dependency>
        <groupId>io.github.tomas-samek</groupId>
        <artifactId>tiko-config</artifactId>
    </dependency>
</dependencies>

<build>
    <plugins>
        <plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-compiler-plugin</artifactId>
            <version>3.13.0</version>
            <configuration>
                <annotationProcessorPaths>
                    <path>
                        <groupId>io.github.tomas-samek</groupId>
                        <artifactId>tiko-processor</artifactId>
                    </path>
                </annotationProcessorPaths>
            </configuration>
        </plugin>
    </plugins>
</build>

The tiko-bom import is the single place the version lives; maven-compiler-plugin ≥ 3.12.0 resolves the annotationProcessorPaths version from it too (3.13.0 pinned above for JDK 23+ — see the note below). The BOM also manages the optional tiko-kafka / tiko-mcp / tiko-test modules.

On JDK 23+? javac no longer runs annotation processing implicitly — the snippet above is already correct (it requires maven-compiler-plugin ≥ 3.13.0). For Gradle, plain javac, and the legacy <proc>full</proc> opt-in, see docs/jdk-23-setup.md.

Scaffold a new project (archetype)

The fastest way to start a fresh project — generates a runnable single-module Tiko DI project with a minimal Main + one @Component, plus AI-assistant context files:

mvn archetype:generate \
    -DarchetypeGroupId=io.github.tomas-samek \
    -DarchetypeArtifactId=tiko-archetype \
    -DarchetypeVersion=0.7.0 \
    -DgroupId=com.example \
    -DartifactId=my-app \
    -DinteractiveMode=false

cd my-app
mvn compile exec:java   # prints: Hello, world!

The generated project ships with AI-context files for the major coding agents — CLAUDE.md (canonical), AGENTS.md, .cursor/rules/tiko.md, .github/copilot-instructions.md, .junie/guidelines.md, .ai-skills/SKILL.md, and .ai-skills/tiko-build/SKILL.md (the orchestrator-model skill — decision tree + @Produces cookbook + anti-pattern redirects). Each tool-specific file points at the canonical sources, so edit one file when conventions change.

Your first service

The three buckets

Every concern in a tiko-built service lands in exactly one bucket. Classify, then write code.

Core — what tiko ships

DI container, scopes (SINGLETON / EVENT / PROTOTYPE), event bus, @EventHandler + @EventTrigger, compile-time validation, lifecycle hooks (@PostConstruct, @PreDestroy, ApplicationStartedEvent, ApplicationEndingEvent), @Configuration typed records.

Plug in — you bring the library; tiko orchestrates the seam

HTTP (Javalin, Jetty, Spark, Vert.x), DataSource (HikariCP, Agroal), schema migrations (Flyway, Liquibase), caching (Caffeine), templates (FreeMarker, Pebble), security (JWT / OAuth via the library of your choice), schedulers, retries, any SDK client. Pattern: declare a factory method annotated @Produces, return the library's value, consume as a constructor parameter. A server that receives the application's requests is a @Component the container starts and stops instead (HTTP cookbook). No wrapper, no adapter layer, no annotation-driven dispatch.

Open design questions

Scheduling-as-tick-event, units of work that nest — the small set of unresolved questions about extending the event model itself. An honest scope note, not a deferral promise.

What you plug in

Lookup-table answer to "does tiko support X?":

| Need | Pattern | Recipe in | |---|---|---| | HTTP layer | A server @Component owning Javalin (or your choice) + plain route methods, one unit of work per request | docs/cookbooks/http.md, example 15_quickstart | | Postgres / MySQL | @Produces DataSource returning HikariDataSource | tiko-build skill, example 15_quickstart | | Schema migrations | Flyway.migrate() in the DataSource producer, before it returns the pool | tiko-build skill, example 15_quickstart | | Kafka | @KafkaSource / @KafkaSink — tiko-native module with compile-time validation | tiko-kafka, example 08_kafka_order_warehouse | | In-process cache | @Produces Cache<K,V> (Caffeine) | tiko-build skill | | Templates | @Produces freemarker.template.Configuration (or Pebble, Mustache) | tiko-build skill | | Security | Javalin before handler + Context attributes (open-design caveat in the model doc §6) | docs/orchestrator-model.md §6 | | Scheduling | @EventHandler on a Tick event published by a small scheduler thread | docs/orchestrator-model.md §4.2 | | Async work | @EventHandler(async = true) for event-shaped work; CompletableFuture / virtual threads for ad-hoc | docs/orchestrator-model.md §4.3 | | Retry | Small utility wrapper — visible code, no AOP | docs/orchestrator-model.md §4.4 | | Configuration | Typed @Configuration records | tiko-config, example 02_config | | Metrics / tracing | Plug in your library; expose via routes on your HTTP layer | — |

Annotations at a glance

| Annotation | Purpose | Deep dive | |-------------------------------------|--------------------------------------------------------------------------|----------------------------------------| | @Component(scope, name, profiles) | Marks a class for DI | di-and-scopes.md | | @Inject

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars3
CategorySecurity
Updated13h ago
Forks0

Languages

Java

Trust signals

92/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 low
tiko-di — MCP Server: Install & Safety Check | SkillAgent