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.
npx agentmods add agents/homenshum/nodebenchai/autonomous_continuation_plangit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.05534 |
| Opus 5 | $0.00000 | $0.02767 |
| Sonnet 5 | $0.00000 | $0.01107 |
| Haiku 4.5 | $0.00000 | $0.00553 |
Grade A, and why
AUTONOMOUS_CONTINUATION_PLAN 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 2d ago.
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.
How it starts
The opening of the file, as written. The whole thing — 434 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Continuation System — Implementation Plan
A unified NodeBench subsystem enabling agents to self-heal from both semantic errors (rollback + lessons) and infrastructure failures (capability-aware model failover + budget gates), so long-running research jobs keep making progress when the user steps away.
Continuation Context
This plan picks up after the cockpit-parity work landed via:
- PR #92 —
feat(chat): full ChatStream port with streaming, attachments, tools - PR #93 —
feat(topnav): kit avatar status panel (pulse + watching + plan + sessions + theme + links) - PR #105 —
fix(theme): dark mode token overrides for kit-scoped surfaces - PR #115 —
fix(avatar): wire dead Upgrade to Team button
Production cockpit is now in exact kit parity for Home, Reports, Chat, Inbox, Me, and the avatar status panel. The next failure mode that blocks dogfood sessions is agent runs that die mid-task — either from semantic spirals (the agent breaks a file, then keeps trying to fix it) or infrastructure failures (rate-limit 429s with no failover). This plan addresses both.
Scope Decision: What Applies to NodeBench
| Subsystem from upstream spec | Applies? | Why |
|---|---|---|
| Visual refinement (gpt-image-2 → wireframes) | No (defer indefinitely) | NodeBench is a research/entity-graph platform, not a design tool. No wireframe artifacts, no Electron main process, no ui_kits/ concept. |
| Report refinement (NodeBench analog) | Defer to v2 | Conceptually: "premium pass on a research report preserving all entities/claims/citations." Nice-to-have, not core to the continuation problem. |
| Time-travel + learning (rollback + lessons) | Yes (core) | Universal agent-spiral failure mode. Convex threads, action timeline, and schema already support most plumbing. |
| Auto-routing + failover | Yes (core, partially shipped) | autonomousModelResolver.ts already has retry/jitter for 429s. Missing: capability tiers, visible switches, budget gates, cross-provider failover. |
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.
- 2d ago First seen · 434 lines · 0 tokens per session scan A 447da23b2d85
AUTONOMOUS_CONTINUATION_PLAN is an agent published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,534 tokens. 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-08-30.
Other agents, from other repositories
ai-readiness-reporter
Runs the AgentRC readiness assessment on the current repository and produces a self-contained, static HTML dashboard at reports/index.html. Explains every readiness pillar, the maturity level, and an actionable remediation plan, framed by AgentRC measure → generate → maintain loop. Use when asked to assess, audit…
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.
chat-agents
Build AI-powered chat interfaces with AIChatAgent and useAgentChat. Messages are automatically persisted to SQLite, streams resume on disconnect, and tool calls work across server and client.
callable-methods
Callable methods let clients invoke agent methods over WebSocket using RPC (Remote Procedure Call). Mark methods with @callable() to expose them to external clients like browsers, mobile apps, or other services.
webhooks
Receive webhook events from external services and route them to dedicated agent instances. Each webhook source (repository, customer, device) can have its own agent with isolated state, persistent storage, and real-time client connections.