Your strategic coding partner for Claude Code and Codex.
Like a cycling domestique, it carries the water, stays focused on your goals, and handles the unglamorous work you don't want to do.
memento — Session Persistence
"Remember Sammy Jankis."
Like Leonard in Memento, Claude can't form long-term memories. Context window fills up, conversation resets, everything vanishes. memento gives Claude its tattoos—session files that persist decisions, progress, and context across resets.
Helps developers embody Flexion fundamentals across conversation boundaries:
- Lead by example — Persists decisions and progress so nothing is lost to "fixed bug" amnesia
- Empower customers to adapt — Enables team handoffs with full context of what was done and why
- Design as you go — Captures evolving understanding as key details emerge during work
mantra — Behavioral Rules
"I told you. You agreed. You forgot. Repeat."
mantra supplies behavioral skills and a fixed reminder on session start and every prompt: assess against evidence, investigate proportionately, and carry the active user objective and authorization forward.
Helps developers embody Flexion fundamentals throughout long sessions:
- Be skeptical and curious — Supports evidence-responsive agreement and challenge
- Never compromise on quality — Keeps assessment, evidence, and required validation in the recurring reminder
- Listen with humility — Revises conclusions for evidence and reasoning while respecting the user's goals
onus — Work-Item Automation
"The burden is mine now."
JIRA tickets, Azure DevOps work items, commit messages, PR descriptions. The awful-but-important work that kills your flow. onus handles the project management bureaucracy so you can code.
Supports GitHub Issues (default, zero-config), JIRA, and Azure DevOps work items.
Helps developers embody Flexion fundamentals while staying in flow:
- Never compromise on quality — Ensures proper commit messages, ticket updates, and PR descriptions
- Lead by example — Handles PM accountability work so it actually gets done
- Empower customers to adapt — Keeps stakeholders informed via trackers without breaking developer focus
agent-artifex — AI-Service Design and Testing
Evidence-based workflows for designing, assessing, implementing, and testing MCP servers, agents, chatbots, and tool-calling systems.
comitatus — herdr Orchestration
Agent messaging, herd initialization, and worktree and agent launches through the herdr CLI. Native herdr and Git handle waiting, reading, and integration; the working lead decides when work is complete and what cleanup may discard. The launcher stays outside the spawned herd by default, and a roster member coordinates it.
Codex launches use --no-daemon; default models are claude-opus-5-5 and gpt-6.1-sol, with explicit overrides supported. Comitatus 1.0.0 removes the separate fan-out skill, role files, and run-workflow helpers. See the comitatus README for the supported commands and migration details. It remains dormant outside a herdr-managed pane.
stilus — Writing and Review
Remove AI slop and review prose for correctness, voice, human readability, and whether the intended point survives.
modus — Work-Item Guidance
Rewrite work items for people, or carry an item through implementation and assess its tests, verification, refactoring, and review evidence. See the plugin's status for the limits of the evidence behind that guidance.
vernaculus — Local-Model Delegation
Delegate well-specified coding work to a locally hosted model through MCP. Its skill guides the caller through reviewing, testing, and refining the draft; it requires a running Ollama server and an installed model.
External (GitHub/JIRA/Azure DevOps)
│
▼ fetch issue details
[onus]
│
▼ populate session file
[memento] ←── "What's next?" lookup
│
▼ read session context
[agent] ◄── [mantra] fixed behavioral reminder through hooks
Each plugin works standalone but gains enhanced behavior when used together.
Historical session-resumption example with Mantra, onus, and memento. Current Mantra hooks use a fixed reminder without a refresh counter; memento retains session state.
| Tool | Version | Used By | Purpose |
|---|---|---|---|
| Claude Code | 2.1.226+ | All | Deliberately tested plugin, skill-preloading, subagent, and parity floor |
| Codex CLI | 0.147.0+ | All | Deliberately tested plugin, subagent, and parity floor |
| Node.js | 24+ | All | Runtime for hooks and scripts |
| git | 2.x | All | Branch detection, commits, session tracking |
Choose the host you use. Comitatus also needs herdr and its agent integrations; vernaculus needs Ollama and an installed model.
When using /onus:fetch, Claude will use these tools to retrieve work items:
| Tool | Platform | Purpose |
|---|---|---|
| GitHub CLI (gh) | GitHub | Fetch issues, create PRs (recommended) |
| Host web/HTTP tools | JIRA, Azure DevOps | API requests when no dedicated CLI is configured |
Note: For JIRA/Azure DevOps, use the authenticated HTTP or web-fetch capability available in the current host.
| Variable | Platform | How to Get |
|---|---|---|
GITHUB_TOKEN |
GitHub | Create PAT with repo scope |
JIRA_TOKEN |
JIRA | echo -n "email:api_token" | base64 (Get API token) |
AZURE_DEVOPS_TOKEN |
Azure DevOps | echo -n ":pat" | base64 (Create PAT with Work Items Read) |
# Check required tools
git --version # git version 2.x
node --version # v24.x or higher
claude --version # Claude Code 2.x
# Check GitHub CLI (optional, for onus with GitHub)
gh --version # gh version 2.x
gh auth status # Verify authentication/plugin marketplace add flexion/claude-domestique
/plugin install memento@claude-domestique
/plugin install mantra@claude-domestique
/plugin install onus@claude-domestique
/plugin install agent-artifex@claude-domestique
/plugin install comitatus@claude-domestique
/plugin install stilus@claude-domestique
/plugin install modus@claude-domestique
/plugin install vernaculus@claude-domestiquecodex plugin marketplace add flexion/claude-domestique
codex plugin add memento@claude-domestique
codex plugin add mantra@claude-domestique
codex plugin add onus@claude-domestique
codex plugin add agent-artifex@claude-domestique
codex plugin add comitatus@claude-domestique
codex plugin add stilus@claude-domestique
codex plugin add modus@claude-domestique
codex plugin add vernaculus@claude-domestiqueCodex users must review and trust plugin hooks before hook-enabled plugins can run lifecycle automation. Skills remain available without trusting hooks.
That's it. No initialization required—plugins load automatically once installed. See each plugin's README for specifics (comitatus, for instance, stays dormant unless you're inside a herdr pane).
Mantra, Memento, Onus, and Comitatus inject context through lifecycle hooks in both hosts. Each plugin defines which events it handles; Codex hooks require the trust described above.
| Hook | When | What Gets Injected |
|---|---|---|
| SessionStart | New conversation | Plugin-specific rules, session or work-item context, or herdr orientation |
| UserPromptSubmit | Each prompt, for plugins that handle it | Status and context refresh according to that plugin's rules |
This means:
- mantra injects its fixed reminder automatically; project rules use the host's native instruction convention
- memento creates session files on first prompt for feature branches
- onus detects issue numbers from branch names and injects work item context
- comitatus injects a short orientation when
HERDR_ENV=1; agents read the herdr skill for its guidance
Each prompt shows plugin status:
📍 Mantra: #3 ✓ | 📂 Memento: session.md | 📋 Onus: #42
Claude Code invokes a plugin skill as /plugin:skill; Codex invokes it as $plugin:skill. The same SKILL.md implements both forms.
Selected entry points are listed below. Each plugin's README explains its usage and requirements.
| Plugin | Command | Description |
|---|---|---|
| memento | /memento:start |
Start new work - creates branch and session together |
| memento | /memento:session |
Show current session status or create new session |
| mantra | /mantra:make-rule |
Create compact project instructions from verbose markdown |
| onus | /onus:init |
Initialize project config (detects commit patterns) |
| onus | /onus:fetch |
Fetch issue details from tracker |
| onus | /onus:create |
Create new work item |
| onus | /onus:update |
Update work item (comment, status, fields) |
| onus | /onus:close |
Close a work item |
| onus | /onus:commit |
Create a commit with validation and format guidance |
| onus | /onus:pr |
Create a pull request with validation and format guidance |
| agent-artifex | /agent-artifex:guide |
Choose an AI-service design, implementation, or assessment workflow |
| comitatus | /comitatus:herdr |
Manage agents, messages, and herds inside herdr |
| comitatus | /comitatus:herd-setup |
Configure herdr command permissions |
| stilus | /stilus:deslop |
Edit prose to remove formulaic phrasing |
| stilus | /stilus:review |
Review finished prose for correctness and clarity |
| modus | /modus:human-work-item |
Rewrite an unclear item for a person |
| modus | /modus:agent-work-item |
Implement an item and assess completion evidence |
| vernaculus | /vernaculus:delegate-to-local-model |
Delegate and verify a local model's coding draft |
Bump plugin versions consistently across all config files:
node scripts/bump-version.js <plugin> <patch|minor|major>
# Examples:
node scripts/bump-version.js memento patch
node scripts/bump-version.js mantra minorThis updates the plugin's package version when present, its Claude and Codex manifests, and the marketplace entry. Bump each modified plugin once per branch after substantive edits; repository-only documentation does not need a plugin bump.
Run workspace tests and metadata validation from the repository root:
npm run install:all
npm test
npm run validate:plugins
# Focused suites
npm run test:comitatus
npm run test:vernaculusPlugins with JavaScript have Jest suites; skills-only plugins use manifest, reference, and fresh-host invocation checks. See AGENTS.md for the Claude and Codex validation commands and skill probes.
Issue-based work follows this repository convention:
Issue #42 (tracker)
↓
Branch: issue/feature-42/description
↓
Metadata: .claude/branches/issue-feature-42-description
↓
Session: .claude/sessions/issue-feature-42-description.md
Mantra's behavior hook injects a fixed reminder in both hosts; its skills and references provide detailed guidance on demand. It does not load project or sibling-plugin rules. The resource hooks automatically inject coverage-labelled observations and periodic reflection on both hosts; their contract owns delivery, storage and measurement limits.
The Mantra README describes injected guidance; FORMAT.md explains rule authoring and host-loading limits. Use make-rule to create custom rules.
MIT