A weekly report of what each agent supports #66

Component

Something else: a test plugin and a weekly automation

Experience

• Owner: each week a report says which plugin parts each installed agent supports, and what changed since the week before. A gap that closes retires its glue, and a break is seen before an operator meets it.
• Operator: hears about a tool's change from the report, not from a broken session.

Proposed behaviour

Rebuild the spike's test plugin in the repository from its description in #61's result comment, under "How this was tested". The plugin's parts:

• a rule with a codeword;
• our real rule-loading hook scripts, plus a marker hook that logs which events fired and which plugin-root variables were set;
• an agent in our frontmatter format;
• a skill using every Claude-only feature;
• a pair of skills where one hands off to the other.

A weekly automation in Superset, the author's agent workspace, re-runs its three probe prompts in every installed agent. It compares the results with the week before and reports the differences. Every agent with a plugin or skills format is installed for the watch, whether or not the plugin supports it yet.

Motivating case

The formats move fast:

• Cursor's CLI started running plugin hooks in August 2026.
• Kiro moved its powers to the Agent Plugins format the same month.
• Kiro's V3 engine becomes the default at the end of October 2026.

The spike's own docs research disagreed with its runs on Cursor's hooks, so only a run tells what a tool does today.

Done when

The report runs weekly and names any change from the previous week.

This is the one scheduled run that spends tokens, so it stays at the three probe prompts per agent.

Depends on

Nothing; it can start now. This is a stream in .freethinking/strategies/multi-tool-plugin.md. Design with /freethinking:hld .freethinking/strategies/multi-tool-plugin.md format-watch.