Borrowing it
Nothing to install: this file belongs to ruanrongman/IntelliConnect. 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/ruanrongman/IntelliConnect/main/AGENTS.mdgit clone --depth 1 https://github.com/ruanrongman/IntelliConnectWrote 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/ruanrongman/intelliconnect/agents-md)<a href="https://agentmods.dev/instructions/ruanrongman/intelliconnect/agents-md"><img src="https://agentmods.dev/badge/instructions/ruanrongman/intelliconnect/agents-md.svg" alt="Measured on agentmods" 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.00735 | $0.00735 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
IntelliConnect AGENTS.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 8d 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 — 30 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
IntelliConnect is a Spring Boot 3.5 / Java 21 backend with a Vue 3 + Vite frontend. Backend code lives in src/main/java/top/rslly/iot/ (controllers/, services/, dao/, models/, param/, config/, utility/). Resources are in src/main/resources/, protobuf files in src/main/proto/, and tests in src/test/java/. Frontend code is under web/src/; docs are in docs/; infrastructure is in docker/. Avoid target/ and generated cache/temp directories.
Compiler & Environment
Use JDK 21 for backend compilation. Local Windows path: C:\Users\Lenovo\.jdks\ms-21.0.9. If the compiler is missing, set IntelliJ Project SDK, language level, Maven Runner JRE, and JAVA_HOME to this JDK. PowerShell: $env:JAVA_HOME='C:\Users\Lenovo\.jdks\ms-21.0.9'; $env:Path="$env:JAVA_HOME\bin;$env:Path". Avoid JDK 17 or JDK 25.
Build, Test, and Development Commands
mvnw.cmd clean compileor./mvnw clean compile: compile the backend.mvnw.cmd testor./mvnw test: run backend JUnit tests.mvnw.cmd clean package -DskipTests: build the runnable JAR without tests.mvnw.cmd spotless:apply: apply Java formatting fromdev-support/dailymart_spotless_formatter.xml.cd web && npm install: install frontend dependencies.cd web && npm run dev: start the Vite dev server.cd web && npm run build: create a production frontend build.cd docker && docker-compose up -d: start MySQL, Redis, InfluxDB, EMQX, and ChromaDB.
Coding Style & Naming Conventions
Use 4-space indentation for Java. Classes use PascalCase, methods and fields use camelCase, and constants use UPPER_SNAKE_CASE. Keep backend changes layered: controllers delegate to services, services to repositories. Run Spotless before committing Java changes. Frontend code follows Vue 3 SFC patterns, ESLint, Prettier, and Stylelint.
Testing Guidelines
Backend tests use Spring Boot Test/JUnit 5; name tests *Test.java and place them under matching packages in src/test/java/. Add focused tests for service logic, controllers, security behavior, and protocol parsing when touched. No frontend test runner is defined; validate frontend changes with npm run build and manual UI checks.
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.
- 8d ago First seen · 30 lines · 735 tokens per session scan A d57c2d22e1d6
IntelliConnect AGENTS.md is an instructions file published in the GitHub repository ruanrongman/IntelliConnect (145 stars, last pushed 7d ago), licensed Apache-2.0. It adds 735 tokens to every session, about $0.0037 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.