dialectic-deriver

dialectic-deriver is an agent for coding agents from Kanevry/session-orchestrator. It costs 181 tokens per session (1,730 once invoked), scanned A, original, MIT.

A read-only reasoning agent that studies recent lessons, past sessions, peer guidance files, and related cards. It proposes carefully grounded updates to the instructions shared between a user and an agent.

In plain words
What is it for?
It is for deriving proposed updates to user and agent guidance from repeated project experience.
Why use it?
It helps preserve useful working patterns without turning one-off events into permanent rules.

Agent

Part of the session-orchestrator plugin — 49 skills, 28 commands, 19 agents, 11 hooks, 1 MCP server shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/kanevry/session-orchestrator/dialectic-deriver
Clone the repo
git clone --depth 1 https://github.com/Kanevry/session-orchestrator

Or install session-orchestrator, the plugin that ships this one along with the rest of its 49 skills, 28 commands, 19 agents, 11 hooks, 1 MCP server.

Wrote 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.

agentmods badge for dialectic-deriver

README.md
[![agentmods](https://agentmods.dev/badge/agents/kanevry/session-orchestrator/dialectic-deriver.svg)](https://agentmods.dev/agents/kanevry/session-orchestrator/dialectic-deriver)
Your own site
<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/dialectic-deriver"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/dialectic-deriver.svg" alt="Measured on agentmods" height="20"></a>
Per session 181 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00181 $0.01730
Opus 5 $0.00090 $0.00865
Sonnet 5 $0.00036 $0.00346
Haiku 4.5 $0.00018 $0.00173

Measured yesterday against content hash 5f2a50debd8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dialectic-deriver 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 yesterday.

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.

agents/dialectic-deriver.md · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dialectic-Deriver Agent

You reason over recent learnings, sessions, peer cards, and project steering to propose updates to the canonical peer cards (.orchestrator/peers/USER.md and .orchestrator/peers/AGENT.md). You are dispatched by scripts/dialectic-deriver.mjs::runDialecticDeriver with a complete payload — your job is to read the payload, decide whether each peer card warrants an update, and emit the full proposed replacement body for any card you wish to update.

Core responsibilities

  1. Synthesise: identify durable, repeated patterns in the learnings + sessions that belong in the per-peer guidance (USER.md = how the user prefers to work; AGENT.md = how the agent should behave in this project).
  2. Be conservative: only propose updates grounded in the supplied inputs. Do not invent new sections that no learning or session supports.
  3. Preserve continuity: if an existing peer-card section is still accurate, keep it. Diff = full replacement body, so omitted sections are deleted — be deliberate.
  4. Respect the model budget: you run as Haiku. Keep your reasoning compact; emit only the blocks you actually want applied.

Autonomy Readiness

autonomy-verdict learnings may justify an ## Autonomy Readiness section in .orchestrator/peers/AGENT.md. Add or update that section only when the supplied payload contains a grounded autonomy-verdict learning or repeated sessions that directly confirm the same readiness status. Summarize the readiness status, confidence, and practical operating constraint; do not infer dispatcher autonomy from unrelated productivity, CI, or preference signals, and do not treat a ready verdict as permission to bypass the configured dispatcher-autonomy dial.

Input format

The orchestrator dispatches you with a single prompt containing a JSON payload:

{
  "meta": { "schema_version": 1, "top_n_learnings": 50, "last_k_sessions": 10, ... },
  "learnings": [ { "id": "...", "subject": "...", "insight": "...", "confidence": 0.9, ... } ],
  "sessions":  [ { "session_id": "...", "completed_at": "...", "issues": [...], ... } ],
  "peer_cards": { "user": { "frontmatter": {...}, "body": "..." } | null, "agent": { ... } | null },
  "steering":   { "path": "CLAUDE.md", "content": "..." } | null
}

Read the full file on GitHub · 140 lines

Changes

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.

  1. yesterday First seen · 140 lines · 181 tokens per session scan A 5f2a50debd8e

Subscribe to this mod's changes

dialectic-deriver is an agent published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed today), licensed MIT. It adds 181 tokens to every session and 1,730 once invoked, about $0.0009 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-09-03.

Related

Other agents, from other repositories

providers

A coding agent runs against a provider account: a login, on a plan, that may or may not be metered. That account has a two-tier balance: included subscription windows that refill on their own clocks, plus paid extra or API usage the provider or the local spend store can name.

rimio-ai/rimz · 0 tokens

model

A coding agent runs in a pane, reports through its own hooks, and appears in the sidebar as one card. This doc owns the model in between: how a native event becomes one durable state per agent, how that state moves, and how the row you see is projected from it.

rimio-ai/rimz · 0 tokens

adapter

Thirteen coding agents report to RimZ, and no code outside crates/rimz/src/agents/ knows which one it is looking at. This doc owns the seam that makes that true: what an adapter is, the contracts it implements, and the path a native hook event walks from the agent's process to the durable store.

rimio-ai/rimz · 0 tokens

adapter_copilot

GitHub Copilot CLI reports through native camelCase command hooks installed as one RimZ-owned user file at $COPILOTHOME/hooks/rimz.json, falling back to /.copilot/hooks/rimz.json. Each command passes its event name to rimz hooks feed --source copilot --event because native payloads carry no event-name field. Hook…

rimio-ai/rimz · 0 tokens

adapter_opencode

This doc is the single home for everything OpenCode-specific. OpenCode's integration surface is an in-process TypeScript plugin, so the adapter ships plugin.ts, embedded at compile time and installed as /.config/opencode/plugin/rimz.ts. The plugin subscribes to OpenCode hooks and bus events, flattens them into a…

rimio-ai/rimz · 0 tokens

adapter_pi

This doc is the single home for everything Pi-specific. Pi's integration surface is in-process TypeScript extensions, so the adapter ships one — extension.ts, embedded at compile time — that forwards each event below to rimz hooks feed --source pi as a fire-and-forget child. The child direction inverts: Claude and…

rimio-ai/rimz · 0 tokens