2.0 KiB
agents
The generic AIMsight agents, one copy of each. An agent states only its trade here; everything specific to a caller (its output paths, its report format, its git rules) reaches it in the request, or through an instruction file the request names.
| Agent | Its trade | Request parameters | Called by |
|---|---|---|---|
analyst |
read a range like the expert and label it, with an analysis that justifies each label | station, range, hints, output folder, DETECTORS: yes | no (with yes, Events: <command>), INSTRUCTIONS: <file> |
Diagnostic-App (instructions/analyst.md, DETECTORS: no) |
tool-builder |
bring the useful scripts of an analysis into the reading harness (tools repository) | the analysis, the tools repository, the path of its report | Diagnostic-App, after the optimisation |
upgrader |
fix the detectors on a range, without overfitting | that of the improve skill |
Optimizer |
validator |
judge the upgrader's modification on every station and family | that of the improve skill |
Optimizer |
Launching them
The repository is a Claude Code plugin (.claude-plugin/plugin.json), loaded read-only:
claude -p "<request>" --plugin-dir ~/agents --agent agents:analyst
In a workflow, through the Agent tool: subagent_type: agents:upgrader, with --plugin-dir ~/agents when the session is launched.
The caller launches from its root, which carries the links data/ (the stations, ~/aimsight-data/data), labeling/ (~/labeling), tools/ (~/tools), and detectors/ (~/detectors) when the agent needs it; it gives --add-dir on their real targets so that the agent can read or write there. Claude does not write into a loaded plugin: what gets written (the tools, the detectors, the sessions) lives in the other repositories, never here.
Taken on 2026-11-16 from Diagnostic-App (analyst, tool-builder, commit dd6f1bf) and from detectors (upgrader, validator, commit 5438b0b). The architecture of the repositories: ~/Diagnostic-App/docs/architecture.drawio.