coprocessor

Enforces dual-process reasoning, memory journaling, and structured output protocols for AI agents.

Updated May 31, 2026
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill coprocessor-alexandernarbaev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coprocessor
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/coprocessor
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill coprocessor-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions lose context after compaction, mix fast and slow reasoning modes, and produce unstructured outputs that are hard to audit. This Skill imposes a layered operating protocol so every agent response is tagged, journaled, and verifiable. ## Core Features & Use Cases - Dual-Process Reasoning: Tags every response as #S1 (fast pattern-match) or #S2 (deliberate analysis) with explicit escalation rules when edits fail or uncertainty rises. - 3-Tier Memory Hierarchy: Journals decisions to a WAL file, persists design specs in docs/specs/, and treats code artifacts as ground truth, enabling context recovery after compaction. - CO-STAR Output Contract & Source Ladder: Structures non-trivial answers into Context/Objective/Steps/Thinking/Answer/References and ranks information sources from official docs (L1) down to model knowledge (L4). - Use Case: During a multi-file refactor, the agent reads the WAL and specs first, tags the session [CTX: refactor], escalates to #S2 reasoning, and emits a CO-STAR-structured plan with journaled decisions. ## Quick Start Activate the coprocessor skill and ask the agent to refactor the authentication module while following its session start ritual and CO-STAR output contract.

Frequently Asked Questions about coprocessor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an AI agent remember context across sessions?

Use a write-ahead log pattern where the agent appends every decision and rationale to a JSONL journal file. On session start, the agent reads the last entries of the WAL plus spec documents to reconstruct context without re-reading all files.

What is dual-process reasoning for AI agents?

Dual-process reasoning splits agent work into System 1 (fast pattern matching for trivial edits and searches) and System 2 (deliberate analysis for refactors and design). The agent tags each response #S1 or #S2 and escalates when edits fail repeatedly or uncertainty exceeds a threshold.

How does the CO-STAR output format work?

CO-STAR structures non-trivial responses into Context, Objective, Steps, Thinking, Answer, and References sections. Trivial single-line answers skip the format, while complex outputs must include all six sections for auditability.

Can the agent detect wrong keyboard layout input?

Yes, the protocol detects accidental RU-to-EN layout mismatches such as 'руддщ' for 'hello' and corrects them silently on read. Ambiguous cases with more than two possible corrections are confirmed with the user and logged to the WAL.

What are the limitations of prompt-based agent protocols?

Prompt-based protocols rely on model compliance and have no runtime enforcement, so an agent may skip WAL journaling or mis-tag reasoning modes under long contexts. They work best combined with external CI checks or hooks that validate artifacts.