streampipes / streampipes-service-core
AGENTS.md756 starsChanged 52 days agoApache-2.0View on GitHub
Applies to streampipes-service-core/. Root AGENTS.md applies as well; build and validation commands live there. - Backend entrypoint and runtime wiring (StreamPipesCoreApplication). - Security setup: WebSecurityConfig, the token filter, OAuth handlers. The list of unauthenticated endpoints is UnauthenticatedInterfaces, applied by WebSecurityConfig. - Startup tasks, migrations and schedulers. Orchestration only — domain behaviour belongs in the *-management modules. 1. Create the class under migrations/v<release>/ (for example migrations/v099/) implementing migrations.Migration: shouldExecute(), executeMigration(), getDescription(). 2. shouldExecute() must make the migration idempotent — it runs…
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 24
Create the class under migrations/v<release>/ (for example migrations/v099/) implementing migrations.Migration: shouldExecute(), …
- Distinctive: line 34
Treat partial failure explicitly — log and rethrow rather than leaving a half-migrated state silently.
- Distinctive: line 40
Do not put long-running or blocking work on startup thread paths.
≈ “Common” is an estimate: at least 1 in 5 of the 36,368 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AGENTS Guide (Service Core)
Scope
Applies to streampipes-service-core/. Root AGENTS.md applies as well; build and
validation commands live there.
Module intent
- Backend entrypoint and runtime wiring (
StreamPipesCoreApplication). - Security setup:
WebSecurityConfig, the token filter, OAuth handlers. The list of unauthenticated endpoints isUnauthenticatedInterfaces, applied byWebSecurityConfig. - Startup tasks, migrations and schedulers. Orchestration only — domain behaviour belongs
in the
*-managementmodules.
High-risk areas
- Authentication flow and the unauthenticated-endpoint list.
- Migration registration and execution (
migrations/AvailableMigrations,MigrationsHandler). - Scheduled side effects (data lake retention, certificate jobs).
Recipe: add a migration
- Create the class under
migrations/v<release>/(for examplemigrations/v099/) implementingmigrations.Migration:shouldExecute(),executeMigration(),getDescription(). shouldExecute()must make the migration idempotent — it runs on every start. Detect the already-migrated state and returnfalse.- Take the storages you need through the constructor;
AvailableMigrationsobtains them fromSpResourceManager(see its constructor for the availableI*Storagefields). - Register it by appending it to the end of the list in
AvailableMigrations.getAvailableMigrations(). Never insert between existing entries: migrations run in list order and installations may already be past earlier ones. - Treat partial failure explicitly — log and rethrow rather than leaving a half-migrated state silently.
Rules
- Preserve startup behaviour for both OAuth and non-OAuth deployments.
- Do not put long-running or blocking work on startup thread paths.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 28,693 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository22 other files it gives its agents.
- AGENTS.mdAGENTS.md
- streampipes-client-go/AGENTS.mdAGENTS.md
- streampipes-client-python/AGENTS.mdAGENTS.md
- streampipes-extensions/AGENTS.mdAGENTS.md
- streampipes-pipeline-management/AGENTS.mdAGENTS.md
- streampipes-resource-management/AGENTS.mdAGENTS.md
- streampipes-rest/AGENTS.mdAGENTS.md
- streampipes-storage-couchdb/AGENTS.mdAGENTS.md
- streampipes-user-management/AGENTS.mdAGENTS.md
- ui/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- streampipes-client-go/CLAUDE.mdCLAUDE.md
- streampipes-client-python/CLAUDE.mdCLAUDE.md
- streampipes-extensions/CLAUDE.mdCLAUDE.md
- streampipes-pipeline-management/CLAUDE.mdCLAUDE.md
- streampipes-resource-management/CLAUDE.mdCLAUDE.md
- streampipes-rest/CLAUDE.mdCLAUDE.md
- streampipes-service-core/CLAUDE.mdCLAUDE.md
- streampipes-storage-couchdb/CLAUDE.mdCLAUDE.md
- streampipes-user-management/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- security-triageSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

