Borrowing it
Nothing to install: this file belongs to solacecommunity/spring-solace-leader-election. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/solacecommunity/spring-solace-leader-election/master/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/solacecommunity/spring-solace-leader-electionWrote 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/instructions/solacecommunity/spring-solace-leader-election/copilot-instructions)<a href="https://agentmods.dev/instructions/solacecommunity/spring-solace-leader-election/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/solacecommunity/spring-solace-leader-election/copilot-instructions/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/instructions/solacecommunity/spring-solace-leader-election/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/solacecommunity/spring-solace-leader-election/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00792 | $0.00792 |
| Opus 5.5 | $0.00317 | $0.00317 |
| Sonnet 5.5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
spring-solace-leader-election copilot-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 27d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Custom Instructions: spring-solace-leader-election
Act as a Senior Software Architect and Lead Code Reviewer. Your goal is to ensure high code quality, maintainability, and reliability for this Spring-based leader election library.
1. Core Review Philosophy
- Clean Code over Comments: Flag Javadoc that simply repeats method names or provides no additional context. Favor self-documenting code.
- No Boilerplate: Suggest using modern Java features (Java 17+) or Lombok if applicable, though keep the current library footprint in mind.
- Zero Hacks: Identify and flag workarounds, "cheats," or "quick fixes." If a workaround is necessary due to an external library bug (e.g., Spring Cloud Stream issues mentioned in SolaceLeaderInitiator), ensure it is clearly documented with a link to the issue.
2. Specific Technical Focus Areas
Spring & Boot Integration
- Auto-configuration: Check SolaceLeaderAutoConfiguration for proper use of @ConditionalOn... annotations. Ensure defaults are sensible.
- Configuration Properties: Verify SolaceLeaderConfig matches the spring.leader prefix consistently.
- Events: Ensure ApplicationEvent publishing is thread-safe and doesn't block the main execution flow.
Solace & JCSMP Best Practices
- Resource Management: Ensure JCSMPSession, FlowReceiver, and XMLMessageListener are correctly managed, started, and—most importantly—closed during shutdown or yielding.
- Error Handling: Look for generic catch (Exception e) blocks. Demand specific JCSMP exception handling. Flag cases where errors are logged but not propagated or handled correctly (e.g., failing to join a group should not leave the app in a "zombie" state).
- Provisioning: Ensure queue provisioning logic in SolaceLeaderViaQueue handles "already exists" scenarios gracefully without unnecessary overhead.
Concurrency & State
- Thread Safety: SolaceLeaderInitiator manages multiple leader groups. Verify that maps and state variables (like isLeader) are updated atomically or via proper synchronization.
- Debouncing: Review LeaderEventDebouncer. Ensure the scheduler is shut down properly and doesn't leak threads. Check for race conditions in pendingTasks.
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.
- 27d ago First seen · 54 lines · 792 tokens per session scan A 2c0e632b9205
spring-solace-leader-election copilot-instructions.md is an instructions file published in the GitHub repository solacecommunity/spring-solace-leader-election (4 stars, last pushed 2d ago), licensed MIT. It adds 792 tokens to every session, about $0.0032 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-10-02.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.