All Claude Code modscdeust/claude-mods
zetetic-insights
The learning loop: every main turn is kept in a ledger across sessions (phase, effort, steps, failed tool calls, agents, advisor calls), joined with the outcomes observed at tool.call (commits kept or reverted, test exits, PR verdicts and merges, no transcript) and the ones /insights writes, and the project's goals; probe sessions are counted and kept out; a phase whose evidence says so gets its tool-loop effort moved one notch, written to a calibration file the autopilot reads. /calibrate apply, /calibrate reset. Starts in observe: proposals are shown, not applied.
The scan could not record a complete footprint for zetetic-insights, so its access is unknown; it passed claude plugin validate on Claude Code 2.1.302.
- Access: unknown, the footprint is incomplete
- Static scan, not a runtime test
Install hint
/plugin install zetetic-insights --marketplace cdeust/claude-modsFrom the repository's own marketplace. Confirm the plugin name in the repository's README before installing. Mods need Claude Code 2.1.287 or later.
Access
Unknown accessThe footprint is unavailable or incomplete.Validation
Passed on Claude Code 2.1.302View the source on GitHub Back to the list
What the scan recorded
- Footprint
- Unavailable or incomplete. Recorded events and calls below may omit access.
- Observed events
- classic hooks, every tool call, subagent spawns
- Hooks
classic.SessionEnd, session.end, session.start, classic.SessionStart {source=clear|resume|fork}, turn.complete, tool.call, prompt.compose, agent.spawn, command.run {command=calibrate}- API calls
$.clock.after, $.clock.now, $.command.register, $.env.get, $.fs.exists, $.fs.list, $.fs.read, $.fs.stat, $.fs.write, $.mcp.call, $.session.cwd, $.session.id, $.state.get, $.state.set, $.store.delete, $.store.get, $.store.keys- Validation on 2.1.302
- Passed
- Scanned revision
b31e9108d9f6- Marketplace warnings
- claude-mods
These are the hooks and API calls reported by claude plugin validate. Access levels describe the widest reach of those calls and are not safety ratings. Validation is a static check, not a runtime test, and a passing result does not prove that a mod works or is safe. How the scan works.
More from cdeust/claude-mods
- cortex-cockpitThe harness cockpit, a viewer: the phase every agent is in (PHASES panel, and main and the running agents in…
- cortex-guardTwo rules no settings hook enforces, refused at the tool call: wiki pages and their generated ADR mirrors are…
- cortex-wiki/wiki <wiki/**.md>: compile a Cortex wiki page (Markdown with ```tikz blocks) to PDF through pandoc and xelat…
- harness-fleetThe owner's interface to the plugin fleet: /fleet shows each owned plugin's installed and offered version, th…
- mission-controlA graphical pane of the harness at work: every agent of the turn as a swimlane coloured by phase, bar height…
- zetetic-autopilotAutomatic effort and model, and a quota that limits how many agents run, not how well one runs. Every request…
- zetetic-geniusGrades every request before its turn starts (task class → effort rung, in one low-effort completion) and rout…
Badge for your README
Authors can show the latest scan result in their README. Each badge links to this page.
[](https://mods.aidojo.si/mods/cdeust--claude-mods--zetetic-insights/)
[](https://mods.aidojo.si/mods/cdeust--claude-mods--zetetic-insights/)