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/tmj-90/gaffer/java-conventionsnpx skills add tmj-90/gaffer --skill java-conventionsgit clone --depth 1 https://github.com/tmj-90/gafferWhat 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.00089 | $0.01242 |
| Opus 5 | $0.00044 | $0.00621 |
| Sonnet 5 | $0.00018 | $0.00248 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade A, and why
java-conventions 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 yesterday.
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write idiomatic, modern Java
Add Java that uses the current language toolset, models data immutably, and matches the repo's existing idioms — provably correct and conventional, not just compiling.
Steps
- Read the lore first. Call
search_lore(Memory MCP) for the repo's Java conventions and target version, and respect the build config (pom.xml/build.gradle), the formatter (Spotless / google-java-format), and any architecture ADRs. Match the Java version the project already compiles against — do not assume the newest. - Find a sibling class and copy its patterns — package layout, naming, error handling, how DTOs/entities are modelled, and how tests are organised.
- Use modern language features where the version allows. Prefer records for
data carriers over hand-written getters/setters or Lombok
@Data/@Value/@Builder. Use sealed interfaces + pattern matching and switch expressions to model closed hierarchies exhaustively; use text blocks for multi-line literals. - Discipline with
Optional. Represent absence withOptionalrather thannull; never call.get()without anisPresent()guard — prefer.map(),.orElseThrow(),.orElseGet(). Never useOptionalfor fields or method parameters. - Favour immutability. Final fields, immutable collections (
List.copyOf), defensive copies at boundaries. Prefer composition over inheritance; extract an interface when it improves testability. - Spring Boot idioms (if applicable). Constructor injection (no field
@Autowired); keep controllers thin and push logic to services; validate request bodies at the boundary (@Valid+ Bean Validation). Log via SLF4J (LoggerFactory.getLogger) — never log secrets, tokens, or PII. - Streams over loops where readability isn't sacrificed; keep methods small and single-purpose.
- Test with JUnit 5 + Mockito. Use
@ExtendWith(MockitoExtension.class),@Mock/@InjectMocks, AssertJ-style assertions, and cover happy path, edge cases, and error conditions. Use Testcontainers for integration tests touching real infrastructure. - Verify + evidence. Run the build's test goal, record
test_outputvia therecord-evidenceskill, and submit for review.
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.
- yesterday First seen · 86 lines · 89 tokens per session scan A 557947f285d9
java-conventions is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 89 tokens to every session and 1,242 once invoked, about $0.0004 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-31.
Other skills, from other repositories
mobile-developer
Expert knowledge in mobile app development for iOS, Android, and cross-platform solutions.
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
telegram-sender
Send and edit Telegram messages, and send photos via Bot API. Use when AnkaLoop needs to send text, reply to a specific message, edit an existing message, send an image, or push proactive notifications (cron results, heartbeat alerts, task status). Requires ANKATELEGRAMBOTTOKEN env var.
security-best-practices
Security best practices and vulnerability prevention guidelines.