Architectural coherence observer for Cos. Called ONCE by the dev loop after it has written a plan and before it implements. Reads the plan against CLAUDE.md and the decision log, and returns a coherence observation. In Phase 1 it is a silent listener — it records and reports, it never approves, blocks, or sends a plan…
An agent that prepares a work summary for a selected period, such as a day, week, or month. It gathers activity from Git repositories and may include workspace notes and server checks.
A read-only agent that runs existing tests for Python, TypeScript, Next.js, Jest, and Kotlin projects. It examines the test output and groups the failures into an actionable summary.
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
Searches the vault for a specific research query and returns one best-match note with excerpt. Targeted mode only in Phase 1. Use when the parent recipe needs to pull vault context on a focused question; dispatch multiple instances in parallel for breadth.
Searches the web for a specific research query and returns a compressed finding with cohort-diverse citations and source-type annotations. Use when the parent recipe needs current-web information — especially fast-moving landscape/tooling topics where model priors can't be trusted.
The engineering skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo, which follow the nitimini lifecycle vocabulary.
Build worker on the routed model - writes code, edits files, executes specs. Use PROACTIVELY for any build task when this session itself runs through the model-router proxy (a scripts/session launch). In a normal direct-login session, do NOT use this agent - use the /fabsol flow's headless delegation instead, because…
Cheap codebase-investigation scout — queries the graphify knowledge graph (graphify-out/) first, then verifies every hit with grep before reporting. Use for "where does X live / how does Y flow / what touches Z" questions before reading files or spawning heavier agents.
Read-only auditor that checks a note, file, or diff for cross-scope leaks before publishing, sharing, or committing. Only applicable when the OPTIONAL wall is enabled — i.e. some scope in AIOS/Systems/layers.tsv declares identifying tokens. Use before any external-facing action (publish, post, send, apply) or when…
Read-only post-publish verifier. Given a published URL (or repo path), fetches the live artifact, runs the cross-scope token grep against it, and traces every first-person factual claim back to the vault's confirmed-history notes — unsourced claims are fabrication-risk. Run after ANY external publish (blog post…
Knowledge archival role for the ARCHIVE stage — the moat's intake. Extracts durable knowledge from the run's artifacts through the strict extraction gate, classifies each entry, writes the reference-tracking writeback, and produces the archive summary. The only agent that writes knowledge.
Import step 3 — distill collected sources + profile into at most 13 standardized draft knowledge entries (the strict gate applies), plus an archive summary. The only import agent that writes knowledge.
1 1mo agoA42 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: