kkRepo java-server.instructions.md

Project-specific Java development rules for kkRepo, a self-hosted service that stores and serves software packages such as Maven, npm, and Docker files.

In plain words
What is it for?
Use it when changing the Java server, database records, file storage, authentication, caching, request responses, or related tests.
Why use it?
They keep package metadata, stored files, permissions, caching, and concurrent requests correct across servers while preserving compatibility with Nexus.

Instructions file for GitHub Copilot

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 instructions/klboke/kkrepo/java-server
Clone the repo
git clone --depth 1 https://github.com/klboke/kkRepo

Made for: GitHub Copilot.

Per session 191 This file is loaded in full into every session.
When invoked 191 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00191 $0.00191
Opus 5 $0.00096 $0.00096
Sonnet 5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

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

Security

Grade A, and why

kkRepo java-server.instructions.md 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.

.github/instructions/java-server.instructions.md · 15 lines

What it actually says

Java Server Instructions

  • Use Java 25 language and library assumptions.
  • Keep transactional metadata in MySQL and blob bytes in the configured blob storage.
  • Use explicit unique constraints and transactions for path, package, version, asset, token, permission, and upload identities.
  • Prefer shared DAO/service abstractions already present in the repository.
  • Do not introduce node-local correctness dependencies. JVM-local state must be a hot cache only and must be reconstructable.
  • For request handling, preserve Nexus-compatible status codes, headers, and response body semantics.
  • Add focused tests for concurrency, duplicate writes, rollback cleanup, permission checks, and cache invalidation when touching shared behavior.
  • Run server checks with mvn -pl server -am ..., not mvn -pl server ... alone.
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. 2d ago First seen · 15 lines · 191 tokens per session scan A 24b927ea557b

Subscribe to this mod's changes

kkRepo java-server.instructions.md is an instructions file published in the GitHub repository klboke/kkRepo (251 stars, last pushed 2d ago), licensed Apache-2.0. It adds 191 tokens to every session, about $0.0010 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.